ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED] FDL file to add user ?...

Post new topic  Reply to topic
 [SOLVED] FDL file to add user ?... « View previous topic :: View next topic » 
Author Message
beth_carlin
PostPosted: Sat Sep 18, 2004 6:29 am    Post subject: [SOLVED] FDL file to add user ?... Reply with quote

Acolyte

Joined: 08 Jun 2004
Posts: 64

Hi WF Gurus,

could you please tell what the best way is to add a user in this situation ?


I am doing a simple one step 'approval' workflow. Enclosed is 'TESTAPP.FDL' There are 3 persons : PERSONA, PERSONB and PERSONC all belonging to the role approver. They all have equal auth.
fmcibie was used to import this fdl into workflow...evrything works ok

There is a need to add more user to role approver in the future after the app is deplolyed .. What I would like to do are :
1) I prefer not to to change the original TESTAPP.fdl evrytime we add a new user
2) I currently have a program to generate a NEWUSER.fdl (see attached) evytime new user is added and then
fmcibie into workflow BUT i am running into this problem
PROBLEM DESCRIPTON :
when a new Create and StartInstance is done, the new workitem still only go to PERSONA, PERSONB and PERSONC
QUESTION:
please tell me what I need to modify in the in the NEWUSER.fdl so that the workitems will go to 4 users : PERSONA,B,C and person XYZ without me having to chg or copy everything from TESTAPP.fdl then include person XYZ ? thx

****** begin TESAPP.fdl *********************************************************************

/*==============================================
Levels
================================================*/
UPDATE LEVEL 0
END 0
UPDATE LEVEL 1
END 1
UPDATE LEVEL 2
END 2
UPDATE LEVEL 3
END 3
UPDATE LEVEL 4
END 4
UPDATE LEVEL 5
END 5
UPDATE LEVEL 6
END 6
UPDATE LEVEL 7
END 7
UPDATE LEVEL 8
END 8
UPDATE LEVEL 9
END 9
/*==============================================
Structures
================================================*/
STRUCTURE 'approval_datainput'
'company_name' : STRING ;
'solution_name' : STRING ;

END 'approval_datainput'
STRUCTURE 'Default Data Structure'
END 'Default Data Structure'
/*==============================================
PROCESS_CATEGORYs
================================================*/
PROCESS_CATEGORY 'approve'
END 'approve'
/*==============================================
Programs
================================================*/
PROGRAM 'Show'('approval_datainput','approval_datainput')
STRUCTURES_FROM_ACTIVITY
EXECUTION_USER AGENT
EXECUTION_MODE NORMAL
WINNT EXE PATH_AND_FILENAME 'fmcnshow.exe'
INHERIT ENVIRONMENT
STYLE VISIBLE
START FOREGROUND
END 'Show'
/*==============================================
Persons
================================================*/
PERSON 'PERSONA'
AUTHORIZED_FOR STAFF
AUTHORIZED_FOR PROCESS_MODELING
AUTHORIZED_FOR PROCESS_CATEGORY ALL AS_ADMINISTRATOR
AUTHORIZED_FOR WORKITEMS_OF ALL
AUTHORIZED_FOR TOPOLOGY
AUTHORIZED_FOR AUTHORIZATION
AUTHORIZED_FOR OPERATION
PASSWORD 'password'
IS_NOT_ABSENT
DO NOT RESET_ABSENT
END 'PERSONA'
PERSON 'PERSONB'
AUTHORIZED_FOR STAFF
AUTHORIZED_FOR PROCESS_MODELING
AUTHORIZED_FOR PROCESS_CATEGORY ALL AS_ADMINISTRATOR
AUTHORIZED_FOR WORKITEMS_OF ALL
AUTHORIZED_FOR TOPOLOGY
AUTHORIZED_FOR AUTHORIZATION
AUTHORIZED_FOR OPERATION
PASSWORD 'password'
IS_NOT_ABSENT
DO NOT RESET_ABSENT
END 'PERSONB'
PERSON 'PERSONC'
AUTHORIZED_FOR STAFF
AUTHORIZED_FOR PROCESS_MODELING
AUTHORIZED_FOR PROCESS_CATEGORY ALL AS_ADMINISTRATOR
AUTHORIZED_FOR WORKITEMS_OF ALL
AUTHORIZED_FOR TOPOLOGY
AUTHORIZED_FOR AUTHORIZATION
AUTHORIZED_FOR OPERATION
PASSWORD 'password'
IS_NOT_ABSENT
DO NOT RESET_ABSENT
END 'PERSONC'
UPDATE PERSON 'PERSONA'
END 'PERSONA'
UPDATE PERSON 'PERSONB'
END 'PERSONB'
UPDATE PERSON 'PERSONC'
END 'PERSONC'
/*==============================================
Roles
================================================*/
ROLE 'approver'
RELATED_PERSON 'PERSONA'
'PERSONB'
'PERSONC'
END 'approver'
ROLE 'Automatic'
RELATED_PERSON 'PERSONB'
'PERSONC'
END 'Automatic'
/*==============================================
Organizations
================================================*/
ORGANIZATION 'XYZ'
MANAGER 'PERSONC'
RELATED_PERSON 'PERSONA'
'PERSONB'
'PERSONC'
END 'XYZ'
ORGANIZATION 'System'
MANAGER 'PERSONC'
END 'System'
/*==============================================
SERVERs
================================================*/
/*==============================================
PROGRAM EXECUTION AGENTs
================================================*/
//PROGRAM_EXECUTION_AGENT
// RELATED_PERSON 'PERSONA'
//END
//PROGRAM_EXECUTION_AGENT
// RELATED_PERSON 'PERSONB'
//END
//PROGRAM_EXECUTION_AGENT
// RELATED_PERSON 'PERSONC'
//END
/*==============================================
Processes
================================================*/
PROCESS 'Approval' ('approval_datainput','approval_datainput')
WINDOW VIEW_REFERENCE_POINT XPOS -8500 YPOS 9490
WINDOW PAPERSIZE WIDTH 20000 HEIGHT 20000
VALID_FROM '2004-07-12 08:00'
CATEGORY 'approve'
DO NOT PROMPT_AT_PROCESS_START
WINDOW SHOW ALL CONNECTORS
WINDOW SHOW NO CONDITIONS
SOURCE 1 XPOS -9135 YPOS 9524
SINK 1 XPOS -8435 YPOS 9224
PROGRAM_ACTIVITY 'approval_task'('approval_datainput','approval_datainput')
LAYOUT XPOS -8435 YPOS 9524
DESCRIPTION '%company_name% %solution_name% '
START MANUAL WHEN ALL CONNECTORS TRUE
EXIT AUTOMATIC
PRIORITY 0
DONE_BY MEMBER OF ROLE 'approver'
DONE_BY ORGANIZATION 'XYZ' MEMBERS_ONLY
PROGRAM 'Show'
SYNCHRONIZATION NESTED
END 'approval_task'
DATA LOOP 'approval_task'
MAP '_STRUCT' TO '_STRUCT'
LAYOUT XPOS -8235 YPOS 9624
XPOS -8335 YPOS 9724
DATA FROM SOURCE TO 'approval_task'
MAP '_STRUCT' TO '_STRUCT'
DATA FROM SOURCE TO SINK
MAP '_STRUCT' TO '_STRUCT'
END 'Approval'



****** end TESAPP.fdl *********************************************************************






**** begin of NEWUSER.fdl *****************************************************************



CODEPAGE 1252
FM_RELEASE V3R4 0

/*==============================================
Persons
THIS FDL WILL CREATE NEW USER XYZ
================================================*/
PERSON 'XYZ'
AUTHORIZED_FOR STAFF
AUTHORIZED_FOR PROCESS_MODELING
AUTHORIZED_FOR PROCESS_CATEGORY ALL AS_ADMINISTRATOR
AUTHORIZED_FOR WORKITEMS_OF ALL
AUTHORIZED_FOR TOPOLOGY
AUTHORIZED_FOR AUTHORIZATION
AUTHORIZED_FOR OPERATION
PASSWORD 'password'
IS_NOT_ABSENT
DO NOT RESET_ABSENT
END 'XYZ'

****end of NEWUSER.fdl *****************************************************************S
Back to top
View user's profile Send private message
jmac
PostPosted: Sat Sep 18, 2004 6:51 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

Hi Beth:

You are running into one of the things that I feel is a real problem with Modeler. It has no granularity when you do exports. ALSO, if you really want to understand FDL, forget about looking at the FDL generated by Modeler, you must look at the FDL generated by Buildtime. Create yourself a quick Buildtime only configuration, use MS Access for the DB, since it is so much faster, then import your FDL (the TESTAPP.fdl file). First let me warn you that the model is going to look ugly, Modeler does not really generate pretty models in FDL (you may already know this from looking at the Graphic Monitor in the clients). Now go and add your person in BT, and be sure to select the role you want this person to have. Do your export and you will see what you need. In my example I have a role called Clerical, and I added a Person "NEWCLERK" with the Clerical role assigned. Here is the Generated FDL.

Code:
PERSON 'NEWCLERK'
  DESCRIPTION ""
  RELATED_ROLE 'Clerical'
  PASSWORD %5E915090A1351F77C0CC19CC9D5E77D0
  IS_NOT_ABSENT
  DO NOT RESET_ABSENT
  GROUP 'FMCGRP'
  SYSTEM 'FMCSYS'
END 'NEWCLERK'


Hope this helps
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
yarlagaddag
PostPosted: Sun Sep 19, 2004 10:07 pm    Post subject: Reply with quote

Apprentice

Joined: 24 Aug 2004
Posts: 28
Location: Bangalore

Hi Beth,

In your FDL file i.e in NEWUSER.fdl file, you have defined the user deatisl etc., but there is no mention of the role to which this user belongs to . In your case, I think this user also should belong to Approver role,to have this user also to perform the tasks. So, in your FDL file, you need to specify the role mapping to this user by specifying RELATED_ROLE field. Or otherwsie, re-generate this FDL file with the Role selection.

Hope this should help!!
_________________
Gopi
Back to top
View user's profile Send private message Send e-mail Yahoo Messenger
beth_carlin
PostPosted: Tue Sep 21, 2004 2:41 pm    Post subject: thx so much for all your help John anfd Gopi. It works...th Reply with quote

Acolyte

Joined: 08 Jun 2004
Posts: 64

nt
Back to top
View user's profile Send private message
JasonG
PostPosted: Thu Sep 30, 2004 10:57 am    Post subject: Reply with quote

Novice

Joined: 02 Jan 2003
Posts: 24
Location: Buffalo, NY

Jmac-
Silly Question- How did you know that the FDL presented by beth was generated by WBI Modeler?- she didn't state that's how she did it in her initial post. Just curious...
Thanks
Jason
Back to top
View user's profile Send private message
jmac
PostPosted: Thu Sep 30, 2004 11:15 am    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

Jason:

So you want me to give away ALL my secrets right.....

OK....

/*
* LEVELs
*/

Buildtime comment for levels.

Here is what the modeler comment looks like

/*==============================================
Levels
================================================*/

Also, I assume that no one other than a modeler user would dump the entire fdl every time.
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
JasonG
PostPosted: Thu Sep 30, 2004 11:17 am    Post subject: Reply with quote

Novice

Joined: 02 Jan 2003
Posts: 24
Location: Buffalo, NY

LOL- Thanks for the secrets...
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » [SOLVED] FDL file to add user ?...
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.