- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-24-2015 12:07 PM
I'm starting to get to grips with Fuji Demand Management but wonder if am missing something?
I can attach Stakeholders based on the Portfolio - good.
These people can be marked as "Assessment Recipient" and they are sent questionnaires during the "Screening" stage - excellent.
They can also be marked as "Approvers" - BUT - I can find no way of getting Approvals sent out to them automatically when I move to "Qualified"?
So - what am I missing?
Mike
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2015 08:00 AM
Actually, I remember having the same issue. There is a business rule that runs on the task table called 'Moot Approvals Upon Cancellation' that cancels approvals when the state of a task record changes to '4'. '4' is usually 'Closed Complete' but for the demand table it is 'Qualified'. I edited that business rule's condition to tell it to not run if the task_type is demand. Try that out and see if it works for you as well.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-24-2015 01:48 PM
I had the same issue. I added a business rule that fires when the state changes to Qualified that runs the script below.
var grStakeHolder = new GlideRecord('dmn_stakeholder_register');
grStakeHolder.addQuery('portfolio',current.portfolio);
grStakeHolder.addQuery('approver','yes');
grStakeHolder.query();
while (grStakeHolder.next()) {
//gs.log('Found an approver for demand ' + current.name);
var grApproval = new GlideRecord('sysapproval_approver');
grApproval.initialize();
grApproval.approver = grStakeHolder.user;
grApproval.state = 'requested';
grApproval.sysapproval = current.sys_id;
grApproval.insert();
}
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2015 12:34 AM
Thanks Adam this looks great. BUT - I have tried this and although the User Approvals are attached as "Requested" they immediately jump into the "No Longer Required" state - any ideas what is causing this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2015 06:46 AM
Have you tried turning on debugging to see what is changing the state value on approval? Probably another business rule or something is running.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-25-2015 07:00 AM
Not tried much debug - but have done some more experimenting. I felt I wanted the APPROVERS to be visible earlier in the process (so that they can be adjusted before start) so I moved the "create" BR to the SUBMIT stage - perfect - they all appear as "Not yet requested". Then I used the "Qualified" BR to set Approval = Requested at which point they all go "No Longer Required"!
So then I started reading WIKI articles on approval and they are all basically couched in "workflow" terms - SO - I thought - I'll have a workflow which attaches at "Qualified" and just contains a "Manual Approvals" entry to pick up Approved or Rejected by the first person and pass it to the Demand Approval field.
BUT this workflow, having attached and moved into the "Manual Approval" node immediately gets CANCELLED! Why? By whom?
So, as you say, something is interfering with the process - not sure where to start with debug - BR logging is horrendous!