@elliemae/pui-scripting-object 1.36.0 → 1.36.1

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

@@ -56,7 +56,7 @@ export type LaunchCategoryOptions = {
          */
         targetType: NavigationType;
         /**
-         * additional query parameters to be passed to the redirect location
+         * additional query parameters to be passed to the redirect location. For example, if rediret requested to services area with targetParams { "key1": "value1", "key2": "value2"}, the url will have querystring as services?query={"transactionId":123, "orderId":456, "key1": "value1", "key2": "value2"}
          */
         targetParams?: Record<string, string>;
     };
@@ -102,7 +102,7 @@ export type LaunchServiceSetupOptions = {
          */
         targetType: NavigationType;
         /**
-         * additional query parameters to be passed to the redirect location
+         * additional query parameters to be passed to the redirect location. For example, if rediret requested to services area with targetParams { "key1": "value1", "key2": "value2"}, the url will have querystring as services?query={"transactionId":123, "orderId":456, "key1": "value1", "key2": "value2"}
          */
         targetParams?: Record<string, string>;
     };
@@ -148,7 +148,7 @@ export type LaunchProviderOptions = {
          */
         targetType: NavigationType;
         /**
-         * additional query parameters to be passed to the redirect location
+         * additional query parameters to be passed to the redirect location. For example, if rediret requested to services area with targetParams { "key1": "value1", "key2": "value2"}, the url will have querystring as services?query={"transactionId":123, "orderId":456, "key1": "value1", "key2": "value2"}
          */
         targetParams?: Record<string, string>;
     };
@@ -201,7 +201,7 @@ export interface IService extends IScriptingObject {
      *
      * After the integration flow is complete, user will be redirected to the location provided in the input parameter.
      *
-     * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?transactionId=123&orderId=456
+     * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?query={"transactionId":123, "orderId":456}
      *
      * Supports EPC & EVP service order integrations
      * @param category - name of the service category
@@ -223,7 +223,7 @@ export interface IService extends IScriptingObject {
      *
      * After the integration flow is complete, user will be redirected to the location provided in the input parameter.
      *
-     * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?transactionId=123&orderId=456
+     * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?query={"transactionId":123, "orderId":456}
      *
      * Supports EPC & EVP service order integrations
      * @param serviceSetupId - unique id of the service setup
@@ -245,7 +245,7 @@ export interface IService extends IScriptingObject {
      *
      * After the integration flow is complete, user will be redirected to the location provided in the input parameter.
      *
-     * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?transactionId=123&orderId=456
+     * Service order transaction id (transactionId) and service order id (orderId) will be appended as query parameters to the url incase of new order. For example, if rediret requested to services area, the url will have querystring as services?query={"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.36.0",
+  "version": "1.36.1",
   "description": "Typescript defintions for Scripting Objects",
   "sideEffects": false,
   "type": "module",
@@ -67,7 +67,7 @@
   },
   "devDependencies": {
     "@elliemae/browserslist-config-elliemae-latest-browsers": "~1.9.0",
-    "@elliemae/pui-cli": "~8.33.0",
+    "@elliemae/pui-cli": "~8.34.0",
     "@elliemae/pui-doc-gen": "~2.0.1",
     "@elliemae/pui-theme": "~2.9.3",
     "@types/styled-components": "~5.1.34",