Java String object containing only digits passed from an IT test to a Javascript script include is coereced to a double value when adding it to a query when interpreted mode is enabled - Known Error

Java String object containing only digits passed from an IT test to a Javascript script include is coereced to a double value when adding it to a query when interpreted mode is enabled Description Because of the behavior of integer literals and other objects being converted to doubles, the AzureEAToSubscriptionMapper fails to find the Azure SA mapping candidates based on the entered enrolment number.

This can be seen in the _findCandidateServiceAccountsForMapping method on this line: nodeGr.addQuery(AzureConstants.NODE_TABLE_ENROLLMENT_FIELD, enrollmentNumber);

The enrolment number has been converted to a double, and the NODE_TABLE_ENROLLMENT_FIELD is a string type field. The query on this table will fail to find any results and as such, the proper mapping will not be generated between the SA and subscription records.

This is just an example of a relatively common behavior when interpreted mode is enabled. If records are missing from a table when they should be created, check in the scripts generating/updating the records in question and verify if any of the queries are using integer literals or for strings that may have been returned from Java that contain numerical values. If interpreted mode is enabled, these values may be converted to doubles, and the query will fail to find the appropriate results. Steps to Reproduce

1. Enable interpreted mode: a. Navigate to sys_properties.list b. Add com.glide.script.interpret.short.expressions as a property with type true | false and value true c. Add com.glide.script.interpret.short.expressions.threshold as property with type integer and value 20000

2. Setup and run the AzureEAToSAMapperIT test class to run against the local instance.

The tests will fail due to the enrolment number passed from Java being coerced into a double.

This can also be reproduced by enabling interpreted mode as above, and calling the createMasterBillingAccountAndMapToLinkedAccounts from the AzureEAToSubscriptionMapper Script Include with an integer literal.

Workaround This problem has been fixed. If you are able to upgrade, review the Fixed In section to determine the latest version with a permanent fix your instance can be upgraded to.

As a workaround, the enrollmentNumber value can be coerced to a javascript string object, by adding a line of code as the first line in the createMasterBillingAccountAndMapToLinkedAccounts method as follos:

createMasterBillingAccountAndMapToLinkedAccounts: function(enrollmentNumber) { var enrollNumber = new String(enrollmentNumber);

var mappingCandidates = this._findCandidateServiceAccountsForMapping(enrollNumber); // Store all the candidates sys_ids before pruning for later use of updating linked accounts var allCandidatesSysIdList = Object.keys(mappingCandidates); this._pruneCandidatesIfMappingExists(enrollNumber, mappingCandidates); this._createMapping(enrollNumber, mappingCandidates); var enrollmentSASyId = this._createServiceAccountForEAIfNotExists(enrollNumber); var subscriptionsSAGr = new GlideRecord(sn_cld_intg_core.Constants.CMDB_CI_CLOUD_SERVICE_ACCOUNT); subscriptionsSAGr.addQuery('sys_id', 'IN', allCandidatesSysIdList); subscriptionsSAGr.setValue('parent_account', enrollmentSASyId); subscriptionsSAGr.updateMultiple(); },

This should coerce the enrollmentNumber variable so that it will be treated as a javascript string, and not coerced to a double value.