cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Workflow - Responsible agent position not in DEV Org. Structure

brian_mogambi
Participant
0 Likes
1,089

Hi,

We have a scenario where I need to assign an agent position to a workflow but the position isn't created in the dev server (screenshot below) as the organization structure is different between dev and production servers.

Is there a workaround to this or we have to enable change mode in production to assign the agent position in the task?

Regards,

Accepted Solutions (1)

Accepted Solutions (1)

mark_daley1
Explorer

Hi Brian,

Instead of assigning the WF to a position directly, it would be better to have assigned it to a Rule (ie to a custom Responsibility rule created via PFAC choose category 'Responsibilities').

In the rule you can assign a position and you could maintain the rule in each system via OOCU_RESP.

Of course this is a change in DEV to what you've built, if you want to keep as is, then I suppose open PRD, or maintain the prd pos in DEV and transport (if it exists in DEV).

brian_mogambi
Participant
0 Likes

Hi mark.daley

Thank you for your response. I'm not well versed with workflow rules and need a little guidance. I've created a custom responsibility rule as seen below to determine the position responsible. However, I've not figured out what to define correctly under the container & responsibility tabs. What field do I pass in the container and how do I assign responsibility?

Container

Responsibility


Answers (1)

Answers (1)

mark_daley1
Explorer
0 Likes

Hi Brian,

You don't have to create a container element,

just create a 'Responsibility' and then choose the 'Assign; button to assign a position (or user etc)

This makes a basic rule with one responsibility and one position assigned (ignore the red icon when creating the responsibility)

You can simulate the rule by clicking the abacus icon.

Note the reason to create a container element would be if you wanted to select different responsibilities based on certain criteria, eg Plant. In which case you create a container element of 'Plant' and then when creating the responsibility you specify the plant eg 1000. Then you assign the position to the responsibility....this way you could have position 123 assigned to plant ABC and 345 assigned to plant DEF...when you test the rule you'd be prompted to enter a plant...

In the workflow you specify the rule ID, you can also bind between the WF container and the rule container , ie plant in above example.