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

container elements not transporting

ross_goodman
Participant
0 Likes
1,050

Hi,

Using PFTC_CHG I have added an element to the container of my workflow template. This went in to a workbench transport request. I activated the workflow template and transported to QA . All reports as being healthy.

When I look in the containier in QA the new element is not there!!

AmI missing some extra step somewhere?

Cheers,

Ross

View Entire Topic
ross_goodman
Participant
0 Likes

TOO quick off the mark!

The 5 elements only show up the SECOND time the rule is called, the first time I can still only see 3 of the elements!

SO at inception (creation of workflow)the rule is called and only 3 elements are visible in ac_container.

After the latest end deadline is reached the rule is called again (same task) and this time all 5 elements can be seen in ac_container.

WTF?

Former Member
0 Likes

Calm down. SAP works just fine. If you have people creating local transports in QAS then you can expect all sorts of problems.

Who knows what else they've been doing.

I would start again from DEV with a fresh copy of whatever you are trying to do.

Let us know if there are any problems and exactly what they are.

Don't forget to do SWU_OBUF after every transport and make sure they're done in the right order and make sure they don't have any errors in their logs.

ross_goodman
Participant
0 Likes

Hi Rick,

It looks pretty much as I acannot achieve what they want to do with the currently modelled latest end outcome anyway. Which brings me to the point where I need to know this.....

The current latest end outcome is modelled to end the workitem and the obsolete line that it follows increases the escalation level and creates a new workitem for the new 'escalation' agent.

I need to stop this happening in a certain instance. So when the latest end deadline is reached I want to have the current model happen if it is agent A but if it is currently agent B I do not want to escalate in effect and more importantly I want the workitem to remain in the inbox of agent B.

So can I put a fork in the outcome of the latest end deadline and have the fork go to a non completion model when the agent is currently user B, but got to completion when other than user B?

Ross

Former Member
0 Likes

Hi Ross,

Keep it simple, just create a new workitem when the deadline expires and set the agent to whoever you want depending on who the agent is now (A -> escalation agent, B -> B).

regards

Rick Bakker

hanabi technology