Hello there,
We are trying to automatize the creation of NELM accounts through API.
(nelm API)
However we would need to precisely know how is the phone attribute validated so we can have at least the same filter on the ServiceNow form.
The phone must be in a E.164 format, but do we have a regex or a list of test?
Are you wanting the NELM UI to enforce E.164 prior to the data being stored in ISC? You should be able to handle this in the transform, but you probably want it validated in the UI Form so that it can be corrected from the person submitting the creation or modification.
To my knowledge the UI form does not provide validation, but you would handle this through a transform. This may be a great enhancement request to submit to SailPoint.
Hey there,
Thank you for your quick response.
I might have not properly explained the need.
The demand is originaly made on ServiceNow, then send via API to ISC.
However the API call can fail if the phone is not properly filled on ServiceNow.
This means that there IS a check made by ISC, that is why we want to be able to do the same on ServiceNow so we can catch the error at the root so the person filling the form can correct it immediatly.
The form resides in ServiceNow, correct?
May be best to reach out to ServiceNow support / forums as there may be more advanced engineers that have specialties with ServiceNow.
We have two forms actually.
The one on ServiceNow, and the one on ISC (the NELM form).
My request lays on the NELM one, as it is there we have an unknown.
When using an API call to create an account directly on the NELM source (No ServiceNow), we can have an error, which means that there is a check done on the ISC form/API.
This is what blocking us on ServiceNow. If we don’t properly understand the innerworking on the NELM form, we can hardly connect it to SNOW.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.