Skip to content

Include use of autoSysFields in scripts #129

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Include use of autoSysFields in scripts #129

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7f3f804
Update README.md to include autoSysField in script
QI-XING Oct 9, 2024
42d74f4
Merge pull request #1 from QI-XING/checks-autoSysField
QI-XING Oct 9, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -329,7 +329,10 @@ It is recommended to use an OOB library for modals in order to improve the user
In your JDBC data load configuration, ensure that the 'last run datetime' option is set to true and configure the target database field to serve as a timestamp, as this best practice enables incremental data loading and improves performance in data integration processes using JDBC.

### Use of setWorkflow(false) in business rules will cause unexpected issues
As setWorkflow(false) method will stop the execution of business rules on that particular GlideRecord object, this will result in unexpected behaviour where the execution of business rules skipped. Maintain caution while using this method and perform regression testing to avoid possible risk. It can have noticeable impact on Audit, Journal fields, notifications, SLA engine, workflow, flow engine etc.,
As setWorkflow(false) method will stop the execution of business rules on that particular GlideRecord object, this will result in unexpected behaviour where the execution of business rules skipped. Maintain caution while using this method and perform regression testing to avoid possible risk. It can have noticeable impact on Audit, Journal fields, notifications, SLA engine, workflow, flow engine etc.

### Use of autoSysField(false) in scripts - backgound
Using autoSysField(false) allows the admin to perform a mass update of records to true up some of the data while retaining the original system audited fields. This is useful to prevent inaccuracy in reporting time critical metrics/performance.

# Additional resources

Expand Down
Loading