This content has been marked as final. Show 9 replies
Yes, i did look at that. They are using the following. They are custom packages. Does this mean that we need to write custom package for each and every process flow which involves approval process?
V_ITEM_TYPE := #V_ITEM_TYPE#;
V_ITEM_KEY := #V_ITEM_KEY#;
P_ITEMTYPE := #V_ITEM_TYPE#;
P_ITEMKEY := #V_ITEM_KEY#;
You will probably want to use a process flow and to kick off the approval flow as step 1, so it would look like:
1. Create user, default end date to today, and send approval notification
2. Read only checks a flag (using flexfield)
3. Kick off another rule in the process to populate flag on approval so your read only check is removed (if rejected, it doesn't move forward in the process). If need be you can add another step in the process or part of the same sql to update the end date with a default end date (3 months out, etc.)
This way while waiting for approval the end date field checks the flag to see if it should allow the field to be editable or not.
I hope this helps.
Thanks once again for trying to get a solution for this.
I have a basic question here before i try that solution. When a notification is generated with approe/reject, do we have a workflow associated with it in the background. If yes, then i understand the system captures the approved status and we can try further one of these solutions.