Browse By Tags
Home
»
All Tags
»
Table Level scripts
»
COM
ASP
Audit Trails
create script
dates
entity level script
Fields
Logging
Regular Expressions
serverside
validate script
Validation
Values() Collection
Workflow
Blog Post:
The Values() collection
Jeff Richards
The Values() collection can be used in all serverside scripts to examine the passed in Values from a form. Create Scripts Validate Scripts Tablelevel Scripts Workflow Scripts The Values() collection must always have an argument passed to it. The Values() collection can not be examined...
on
13 Mar 2009
Blog Post:
Using a Table Level Script to Track Changes to Data Made by Users.
Jeff Richards
This article uses an idea first mentioned in " Validation Rules Don't Always Mean Stop! ". The example 'UpdateRecord' event function below will write out into a log file which fields have changed. It won't write every field in the screen so we first need to know what fields...
on
7 May 2010
Blog Post:
Validation rules don't always mean "Stop!"
Jeff Richards
I was asked recently about how to create a log of when data was changed within a particular screen. Now the requirement was focussed on the screen and not on the the record. If we had been interested in whenever data in the record changed then of course we could use an Update event function within a...
on
13 Mar 2009
Blog Post:
Objects Available in the Internal COM API
Jeff Richards
The diagram below contains the objects, methods and properties that are the main ones used in the internal COM API of Sage CRM. These objects can be used in field level scripts; Create and Validate and also in TableLevel scripts and Workflow JScript conditions. The are sometimes...
on
13 Mar 2009
Blog Post:
Validation of Dates
Jeff Richards
The validation of dates can be tricky. Partly this is due to jscript and partly down to the flexibility that Sage CRM provides in allowing dates to be presented. I have covered how default values dates can be controlled in the article: Populating Default Date Field Values Other Date related articles...
on
29 Dec 2008
Blog Post:
A Universal "Go Back" button in Workflow
Jeff Richards
The requirement to allow the user to fall back to an earlier point in the workflow is usually handled by looping. We can see from the diagram below how a workflow can allow a user to drop back and repeat or cycle through certain workflow states again and again. But what if we need to have a workflow...
on
1 Nov 2009