The Prolecto Record State Manager (RSM) offers a scalable record management pattern where a series of rules and criteria can be set to move any NetSuite record from one state to another. Rules are visible to users and can be overridden by selected roles even if programmatic checks do not meet criteria.

Organizations with high transaction inputs and management need to focus on only the exceptions. Rules and states are used to drive pipelines revealing the orders that need attention and providing comfort that all transactions that pass rules can do so fully automated.

Prolecto Resource: Record State Manager Demonstration

See how to operationalize scalable sales order practices in NetSuite using native tools—without recurring fees or compromises to process control.

Build ID 113

Version: 20221104.RC

Minor revision related to SuiteScript 2.1 implementation.

---

Version: 20221019.RC

Support for SuiteScript 2.1 plug-in technologies.

---

Version: 20220110.RC

Support for the advanced setting: "skipintermediateStates". Includes performance enhancements should no changes in the state since the last review, do not do update record updates.

---

Version: 20211110.RC

Refinements for auto status changes.

---

Version: 20211004.RC

New map/reduce capacity to override a rule using Prolecto Queue Manager.

---

Version: 20210603.RC

Better control over how optional rules are treated when they have not yet been added to a specific record, but the advancement of a record state/status depends on them.

---

Version: 20210323.RC

• Added support for new ADVANCED SETTING “backgroundExecutionControlField” (see above)
• With the new field, you can control RSM (by record type) so that it will perform NO work during a User Event script, but will instead always write a record to QM to have the evaluation done in the background.

---

Version: 20210316.RC

1. Switch for Checking all rules when "Do not check until"? 2. Map / Reduce for PRI_RSM queues

---

Version: 20210204.RC

A rich parameter is now available to evaluate many different records and record types to allow them to be in a hierarchical order so that grandchildren are evaluated first, then children, and finally the parents.

---

Version: 20210121.RC

Refinements to engine algorithms.

---

Version: 20201115.RC

• Added better support for Inbound Shipment record by honoring a flag in the “advanced options” field of the PRI RSM Record Type record. 

• Added support in the Map/Reduce script which allows you to evaluate many records at once.  Previously it had to be a non-grouped search, so that each row returned a record type and record id.

---

Version: 20201012.RC

Enhanced so that you can set additional fields on the rule instance record. Two new functions are exposed: ruleInstanceBeforeSubmit and ruleInstanceAfterSubmit

---

Version: 20200922.RC

Better support for mass evaluating records and respecting if other jobs already triggered the same work.

---

Version: 20200824.RC

Supporting a new plug-in capacity to call events before and after rule instances are created to give more control over other business records and logic.

---

Version: 20200807.RC

Refined rules so that evaluation sequence can be respected.  Under general situations, sequence does not matter.  But dependencies between rules might be better expressed when order matters.

---

Version: 20200728.RC

1. Added support for evaluating rules in a WorkFlow (instead of in a script via the plugin, or using the “saved search” concept).
2. Additional Role field on Rule to control which roles have permission to Add Optional/Ad Hoc Rules
3. Override Button CSS Attributes
4. Rule Form Redesign to fit new capacities

---

Version: 20200713.RC

Minor revision for a small error.

---

Version: 20200611.RC

1. RSM Rule summary table on main page has the option to stretch into its own section to a full width (98%)
2. Wrap try/catch for each rule evaluation so that a single error does not cause remaining rules to not fire.

---

Version: 20200313.RC

Minor revision.

---

Version: 20200311.RC

Normally, once a rule is “manually overridden” – it remains that way forever.  The new method allows (via script) to “clear” a rule which was previously overridden.

---

Version: 20200303.RC

Refinements for two clients specific situations.

---

Version: 20191231.RC

A new feature is the support for multiple plugin implementations.  Prior to this, you needed to use a single plugin implementation script, and so if it had to handle multiple record types, you had to use evaluate conditions in all the functions.


You can still take that approach, or you can create separate implementations for each record type.  The scripts are fully backwards compatible, so that if we upgrade the bundle for a client, it will continue to use the only implementation that exists in that account.


 


So no rush on this, but if you could revision one more time to the 20191231.RC, we should be all set.

---

Version: 20191230.RC

New method for the custom plugin called “markIncomplete” which the RSM engine will call if it evaluates a record and determines that the record has failed one or more rules.

---

Version: 20191205.RC

Feature to send an additional flag to the plugin to tell it the ExecutionType from which it was called (eg CREATE or EDIT).  Some rules we may not want evaluated on Create.

---

Version: 20191028.RC

For non-native NetSuite states (custom states), we can allow the state to go backwards (back to a previous state as criteria changes).  

---

Version: 20190702.RC

Several key enhancements:

1. Ability to “reverse” the search logic for the RULE EVALUATION field.
2. Ability to configure a DO NOT CHECK UNTIL setting
3. Ability to control exactly which statuses will show in the Rule Summary Table
4. More granular CSS classes on the Rule Summary Table

---

Version: 20190204.RC

Tthe new features are:

·         Currently RSM only stores when a rule has changed its status (on the rule instance record).  A client wanted the option to also store when the rule was last evaluated

·         Ability to optionally store on a record whether RSM will evaluate a record (or whether it already deems it “complete”)

·         Created new “Rule Debugger” suitelet which lets you run RSM against a record in “non-updating” mode, so that you can check the rules, but they won’t update anything.

---

Version: 20190116.RC

Minor bundle maintenance.

---

Version: 20181210.RC

Add an optional script parameter to a Map/Reduce script

---

Version: 20180822.RC

Added support for Optional Rules, and Ad-Hoc Rules, and a new Rule Category for organizing rules. Added more customization options to display information in the client's preferred terminology. Added ability to override multiple rules at once using a suitelet view on the target record. Added ability to add optional and ad-hoc rules to a record.

---

Version: 20180530.RC

Minor refinement.

---

Version: 20170529.RC

Support for more options for CheckComplete functions.

---

Version: 20170516.RC

Support for X-Edit operations to allow for bulk updates on records.

---

Version: 20170313.RC

Initial release as a migration from Transaction Approval Manager.

---