Blog

A Blue Mountain RAM rule can do many things. The idea is to select and sequence available behaviors with the goal of implementing and enforcing your organization’s business processes. You will need to know what a rule can do, and what your business processes need to do. Then you can translate your process for a record into a rule. The following list presents many of the things a rule can do.

  • Organize Steps Of Record Processing Into Logical Chunks Called States
  • Control Records With States For Negative As Well As Positive Conditions
  • Sequenced States = Sequenced Workflow
  • Control Who May Create Records Under This Rule
  • Control Who May Edit A Record During Each Of Its States
  • Control Who May Transition One State To Another –On A Per Transition Basis
  • Specify Allowable Data Entry In Fields And Grids For Each State Of The Rule
  • Lock A Field, A Grid, Or A Record Based On The State Of The Record
  • Control The Adding And Removing Of Listings Within Record Features
  • Collect Electronic Signatures
  • Collect Electronic Signature Reasons
  • Automate Transitions Based On Completed E-Signatures
  • Require An E-Signature Before Transition Is Allowed
  • Send Notifications Triggered By E-Signatures Or Transitions
  • Send Notifications When Record Data Changes As Per Specified Criteria
  • Send Notifications Telling People About A Record They Are To Sign
  • Automate The Creation Of New Records Based On A Record State Transition

Security In A Rule Design (User Rights): The Big Picture
Regardless of what rights a user is granted anywhere else in the system, if the rule governing a record the user is working with does not specify that user may do a certain activity with the record, than that user may not. The rights assigned in a rule are very important. A “deny” in a rule always outweighs any number of “allow” settings elsewhere.