Skip to content

gs.info() instance check #141

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.

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 11 commits into from
Closed

gs.info() instance check #141

wants to merge 11 commits into from

Conversation

Rampriya-S
Copy link
Contributor

The gs.info() statement can be used to write information to the system log. It is generally used when debugging. Using gs.info() statements will pollute the system log. Prior to promoting artifacts to a production instance, debugging statement should - in most cases - be removed.

Rampriya-S and others added 11 commits October 14, 2024 09:31
…st Framework to ensure functionality after updates and deployments.
…n service portal. Instead we should use AngularJS equivalent capabilities to achieve the same.
…n service portal. Instead we should use AngularJS equivalent capabilities to achieve the same.
…It is easier to read, it gives the compiler a chance to optimize your code, and it's mostly faster too.
…sent in Client scripts, Business rules and Script incluedes
…Test Framework to ensure functionality after updates and deployments.
…Test Framework to ensure functionality after updates and deployments.
…nt scripts, Business rules and Script includes.
@Rampriya-S Rampriya-S closed this Oct 15, 2024
@Rampriya-S Rampriya-S deleted the gs_info branch October 15, 2024 17:34
@Rampriya-S Rampriya-S restored the gs_info branch October 15, 2024 17:34
@Rampriya-S Rampriya-S deleted the gs_info branch October 15, 2024 17:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant