@elliemae/pui-scripting-object 1.34.4 → 1.35.0

package/dist/types/lib/objects/auth.d.ts

@@ -9,6 +9,9 @@ export type User = {
      * unique identifier for the user
      */
     id: string;
+    /**
+     * legacy tenant id
+     */
     realm: string;
     /**
      * user's first name
@@ -54,6 +57,10 @@ export type User = {
      * NMLS number
      */
     nmlsOriginatorId: string;
+    /**
+     * instance id
+     */
+    instanceId: string;
 };
 /**
  * token type

package/dist/types/lib/objects/service.d.ts

@@ -187,7 +187,7 @@ export interface IService extends IScriptingObject {
      *
      * After the integration flow is complete, user will be redirected back to the url provided in the options.
      *
-     * Service order transaction id and service order id will be appended as query parameters to the redirect url incase of new order
+     * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the redirect url incase of new order. For example, if redirectUrl is services, the final url will be services?transactionId=123&orderId=456
      *
      * Supports EPC & EVP service order integrations
      * @param category - name of the service category
@@ -209,7 +209,7 @@ export interface IService extends IScriptingObject {
      *
      * After the integration flow is complete, user will be redirected back to the url provided in the options.
      *
-     * Service order transaction id and service order id will be appended as query parameters to the redirect url incase of new order
+     * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the redirect url incase of new order. For example, if redirectUrl is services, the final url will be services?transactionId=123&orderId=456
      *
      * Supports EPC & EVP service order integrations
      * @param serviceSetupId - unique id of the service setup
@@ -231,7 +231,7 @@ export interface IService extends IScriptingObject {
      *
      * After the integration flow is complete, user will be redirected back to the url provided in the options.
      *
-     * Service order transaction id and service order id will be appended as query parameters to the redirect url incase of new order
+     * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the redirect url incase of new order. For example, if redirectUrl is services, the final url will be services?transactionId=123&orderId=456
      *
      * Supports EPC & EVP service order integrations
      * @param providerId - unique id of the service provider

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@elliemae/pui-scripting-object",
-  "version": "1.34.4",
+  "version": "1.35.0",
   "description": "Typescript defintions for Scripting Objects",
   "sideEffects": false,
   "type": "module",
@@ -63,8 +63,7 @@
   "jestSonar": {
     "reportPath": "reports",
     "reportFile": "tests.xml",
-    "indent": 4,
-    "sonar56x": true
+    "indent": 4
   },
   "devDependencies": {
     "@elliemae/browserslist-config-elliemae-latest-browsers": "~1.9.0",