Solutions for User Decision step- Upon reject, auto-popup text for reason

[Former Member]

Execute user Decision workitem, when user click reject button, open text for rejection reason within the workitem.

Ideally, for the auto-pop text , we need a descriptive header and user can enter reject reason. Text must be added before the workitem can be saved.

Any thoughts.

Thanks a lot.

[pokrakam · Accepted solution]

After 'reject' outcome, add a new step, create a task based on SOFM.CREATE. In your binding you can default a subject.

Bonus on using this way: It's visible as an attachment in all subsequent tasks, no need to fiddle with putting the description into other steps' texts and everyone can see it.

Cheers

Mike

[Former Member]

Further questions:

1. Using SOFM.CREATE. A word document opened. After I enter text and save, I received error message 'Word can not complete the saving due to a file permission error'. How to resolve error?

2. once the SOFM object created, do I need to append it to workflow container attachobjects? Right now the SOFM OBJECT doesn't appear on the attachment list automatically.

[Former Member]

yes, on the SOFM.Create-Task use a dataflow from the WIOBJECT_ID => (append table) ADHOCOBJECTS

This will popuplate this rejection to the hyperlink-section of the workflow.

You may also activate the outcome-even "user-cancelled" in the workflow definition (or by copying the coding to your own method that could do it) and loop around back to the user decision if he cancels the document create (which I found out is sometimes a problem for the users).

I also have made the experience that it is quite the same effort and more convenient if you design a complete user-driven screen. Then you have full control of that issue. I always use a small dialog box with a textEdit-Control where the users have to enter their rejection reason.

I then create my own ZWFNOTE-Object and append this to the ADHOCOBJECT. This usually works very fine.

with kind regards,

Florin

[mark_rodrigues_rt]

Hi In addition , make sure that the "Advance with Dialog" option is checked in the step that grabs the rejct reason. That way it should appear semaless to the user.

You may have grab the _WORKITEM container element, so that you have a workflow container element that contains the agent that performed the decision (although may not be required if your decision will always).