As Approval of Action Items through XOG is not designed in suitable way for us, we would like to know if exists some safe way how to remove Assignees from AI which were already sent. Is this somehow possible? (through XOG maybe)E.g to remove one of this user:
Thanks a lotMatej
There is no way to remove the action items through XOG which already sent.
I agree with Senthil. No supported way of achieving this.
Completely agree with Debroop and Senthil.As there is now way to remove the action item from XOG although we can update the state of an action item via XOG.
Refer the below XML:<NikuDataBus> <Header action="write" externalSource="NIKU" objectType="actionItemApproval" version="12.0"/> <actionItemApprovals> <actionItemApproval actionItemDbId="5038001" assigneeDbId="5038001" processDbId="5084022" status="CAL_CLOSED" /> </actionItemApprovals></NikuDataBus>
But if any process is associated with the action item then it will get stuck.Or we can remove the action item directly by updating the database but that is not recommended by 'CA' and it will also stuck the process.
Note: It will work only for the logged in user.
While I agree with the above responses that what you're asking isn't possible, at least not easily, it might help to ask what you're trying to accomplish. Why are you needing to remove people from action items, and perhaps more specifically why are unnecessary people being assigned to begin with? If we better understand the issue, there may be another way to solve it.
Hi, thanks to all who posted some idea.
As this was a blind way for us, we have decided to completely re-work the process. Point is that we have 2 PMs on each project. Our customer wants to send AI to both PMs. That was able to do by a configuration, but not easy.
Then condition for approval is to have approval (at least) from one PM (but can be both) to have Project as approved. Of course end user can have a lot of projects in his Submitted Timesheet. We thought that removal of AI can help us to solve the approval condition (PM1 or PM2) which couldn't be configured in Manager approval process.
The process could be checking:
Number of assignees with Status Approve >= 1
As soon as one 'PM' approves the action item, the process will continue on.
of course we can't use this option. Imagine you have 3 project with different PMs. That are 6 PMs.
From each project we need approval from at least one PM (but can be both). That condition cannot be configured (we don't know about that possibility).