Folks - still relatively new and trying to get a feel for where the rules engine is going. right now, the lack of a central rules repository and the inability to duplicate rules can make for some tedious sessions. I assume those features are coming?
On a more near term note: I’m trying to reconcile a “master” or global/Exec status project and a number of, let’s call them “local”, projects where the work is getting done in the field. As such I have a Global custom task status in my library that I use in the Exec project and I multi-home it in the local projects (where its hidden). And then in the local projects they have a variation on that custom status field but specific to the work being done in that project (they get “mapped” to the global status choices so portfolios work nicely with common statuses across the board). Let’s call the local project field the local task status.
I have rules in the local project that when the local task status changes, the global status is made identical so the execs see the current status in the exec project . There is also a “sync” custom field in both projects that shows “clear” when the two match and “mismatch” when they don’t.
The reason for this is the Global task status when warranted can be manually updated by the execs in the master project. Actually, there are tasks in the master project that aren’t multi=homed so the need to utilize the status field in the exec project is needed,
So this setup requires a “sync” reconcile rule for each status so at least folks know there is a mismatch that needs to be resolved. And for the occasions where status might need to be pushed down. I DON’T want execs in the local projects. Only the critical tasks than need to be multi-homed show up in the Exec project.
Is anyone else running a setup like this?
Anyway - I’m in mirror-rule hell at the moment (would be worse if for the new ‘otherwise’ construct!). Is the following table correct so I know if I’m barking up the wrong tree trying to get some economy of rule building:
|Feature|. |Available?|
|Trigger on any field mismatch|. |❌ Not natively supported|
|Compare two fields directly (A ≠ B)|. |❌ Not supported|
|Trigger rules on multiple field changes at once|. |❌ Only one field per trigger|
|Trigger on “Field is changed” (generic)|. |✅ Yes|
|Trigger on “Field is changed to [specific value]”| |✅ Yes|
|Use “Otherwise” for binary sync check.| |✅ Yes|