- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-12-2017 03:51 PM
Running in Helsinki and going nuts trying to figure out why the process flow does not work consistently.
I have a process flow setup on the dmn_demand table. I have a total of 7 process flow entries for the dmn_demand table. I cannot, for the life of me, understand how the system figures out the previous states to determine if a check box should be entered on the PF. The condition to determine the current state always works properly. The PF is underlined for the current state and move accordingly. However, the previous PF entries don't get checked off. (Well, some do and some don't....and if I delete and recreate the PF entry with the same settings, it may enter a check box, or may not) I assume (since I can't find any documentation on how the check box is determined, that it is sorted by the order of the PF entries. Therefore, if the current PF is at 9, all entries with a value of < 9 would display a check box. This does not appear to be true. Here are some screen shots showing my PF table entries for the dmn_demand table and what a sample record shows in the form view.
My 7 entries are listed in an order that matches how the demand workflow runs.
Note, I have put the same value in the "name" field only as a test. If I use a descriptive name in there, it will sometimes remove the checkbox that was working when I had a number in there.
Any help would be appreciated. There does not appear to be any logic involved in how this is operating.
Solved! Go to Solution.
- Labels:
-
Change Management
-
Incident Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-13-2017 12:26 PM
Ok, so I think I have this figured out, although it doesn't make a lot of sense.
I noticed that if I changed the name of the Flow Formatter in the PF table, the check boxes would get removed from that state. I also noticed that the states I was having issues with, were states where the name did not match the state, but rather the order. So, I changed the name of the entries in the process flow formatter table so that it matches the state. Now everything works.
Posting screen shots of what I did:
Modified the Name field on the table to match the state for that chevron.
After doing this, the previous state that wasn't showing a check box (Qualified) is now checked appropriately. I also have the visited sites field showing in this form for reference.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2020 04:36 PM
I wanted to add a bit more clarification on root behavior behind this. The Demand (dmn_demand) table has a column called visited_state. As you transition through the states, you can look at this column and it will add the state values as an array for each change to this column. For example, if the Demand goes from Draft (1) to Submitted (2) to Qualified (-4), you will see the values 1, 2, -4 in the visited_state column.
I made the scenario on purpose above where I skipped the Screening (3) to show that it's possible with out of box behavior to jump directly to Qualified and skip Screening. In this case where Screening is skipped, the Process Formatted will NOT show the checkmark for that state because 3 is NOT found in the visited_state field which has 1, 2, -4.
So, in summary, whatever values are stored in the visited_state column and have a match to a Process flow model (sys_process_flow) entry then that formatter box will have a checkmark. The current state will have a blue underline versus the check mark but notice current state is also stored in visited_state.
Lastly, here is an example of where Screening was skipped with out of box behavior:
Feel free to mark helpful if you found this valuable. I know I struggled with it at one point too.
p.s., make sure you review all business rules when you are customizing the state value column. For example, go to BR list, filter on your table, where active=true and script contains state. This will whittle your list down quite a bit. The few BRs that are really important for state include the following.
- State Changed Back to Draft
- Update Assessment Metric Result on Updat
- Demand Active State Management
- Update Visited States on state change (this one updates the visited_state column)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2021 12:13 PM
Hello
I was trying to follow this thread and am still struggling with how to get our Demand Process Flow state of 'Sequenced' to show a checkmark after it moves to the 'Scheduled' state.
The Flow Formatter shows the 'Name' and 'Condition' columns have the same values, as shown here:
And this our 'Update Visited States on State Change' Business Rule:
I'm not very experience in scripts or business rules, etc., so not sure where to look.
Any assistance would be appreciated.