Release 42 ( CORE )

Product Version: CORE – Release 42 Notes - The following Tasks have been completed/fixed in this release.

Task 35782 - ENHANCEMENT

SSO should support multiple PrismHR systems

Resolution:

The ClientSpace system has been enhanced to allow SSO to support multiple PrismHR systems connecting to a single ClientSpace Installation.

Task 35962

Increase Number of characters in Email Template Template Code field in UI

Resolution:

The Template Code field of Email Templates has been extended from 10 characters to 100 characters to support longer code values. This will help when setting up multiple templates, allowing for more robust and descriptive TemplateCodes

Task 36041

Delete Calendar Event issue

Resolution:

Corrected a bug that caused all occurrences of an appointment to be incorrectly deleted in Outlook when a single occurrence was deleted in ClientSpace.

Task 36054

Import Queue should respect API Configuration records

Resolution:

Corrected an issue where under particular circumstances if the ClientSpace installation was configured to use multiple PrismAPI configurations, the API Import Queue would allow records to be inserted that were not attached to an API Configuration. The Import Queue now requires a foreign key to an API Configuration for all records.

Task 36086 - ENHANCEMENT Click here for the video

Set field from Pattern Business Rule

Resolution:

A new Core business rule _SetFieldValueFromPattern has been created that has the ability to extract the first instance of a value from within a text field using a .Net RegEx pattern and set the value of another text field on the same page to this extracted value. This business rule operates based on the following:

The SourceField value will always be treated as text
TargetField must be a Text data type
TargetField will ALWAYS be overwritten with the results of the pattern match
SourceField and TargetField must be on the current dataform and cannot be used on tabbed forms
If the pattern match returns no value, the TargetField will be cleared

For help configuring this rule, contact your NetWise account manager

Task 36144

Template Task Start and Due Dates

Resolution:

Corrected an issue in Template tasks that would affect the start and end date offsets where these were derived from an attribute dataform.

Task 35869 - ENHANCEMENT Click here for the Video

Import Users - Phase one

Resolution:

The nightly import process has been enhanced to allow the import of User records into the system either by inserting new records wholesale, or by cloning an existing user record based on the presence of a "CloneAUser" flag on the import file. Phase one of this process by necessity contains the following restrictions/caveats:

Cannot import global admin
Department must be an integer (no foreign key lookup at this time)
AdHoc Profile, integer (no foreign key lookup at this time)
Time Zone, integer (no foreign key lookup at this time)
Domain, integer (no foreign key lookup at this time)

User Cloning

Cloning a User is only possible during Add
'CloneAUser' and 'CloneFromUser' are fields that manage cloning
'CloneAUser' indicates a User should be cloned
'CloneFromUser' is the ImportID of the User to be cloned
If 'CloneAUser' is empty (or "0"), no User will be cloned
If 'CloneAUser' is set (equal to "1"),
- If the import process was unable to locate user by CloneFromUser = User.ImportID, a Hard Error is returned in the Import log file
- If 'CloneFromUser' is a valid User, that User will be cloned. Workspaces, Roles and Modules will be cloned if set in the Import file

Password

If provided, will be encrypted and set, Force Password Change flag will be cleared even if set in the Import Row
If not provided, Force Password Change flag will not cleared, will be set to the value in the Import Row

For more information about how this new functionality works, or for help configuring, contact your NetWise Account Manager

Task 36207

Email Integration Issues

Resolution:

The email integration has been enhanced to utilize the Host field of the API configuration form when attaching to a mailbox, allowing for mail applications such as GoogleApps which support client domains. Email addresses are no longer required to end in provider specific domains such as 'gmail.com'

Task 35874 Click Here for the Video

Email Templates

Resolution:

The new Email Template architecture has been enhanced to allow notification templates to be configured that run on any dataform save like a template task. Triggering for this functionality mirrors Link Configuration, including condition expressions.

Trigger conditions can be configured based on the associated dataform fields, or from data returned via Server Data Procs.
An email template merge has been added to the dataform save architecture. This allows configuration for custom notifications utilizing field replacement data from a custom stored procedure.
Mail recipients of the notification are currently also retrieved from a custom stored procedure
Dataform field delete has been enhanced to check if there are template conditions that use the field being deleted.

Form more detailed information, read Configuring Email Template Triggering in ClientSpace.

Error rendering macro 'contentbylabel' : Could not parse cql :