Genesys Cloud - Developer Community!

Hello,

We have a requirement to change the Integration/ Category on DataActions. We have observed that there is API

'patch /api/v2/integrations/actions/{actionId}' which allows to enter the Category to patch with the action. Would like to know if this would work updating the Integration associated to the DataAction and if so, are there any negative impacts of using this API and once Action is updated, do we need to republish the Architect Flows using the updated DataActions?

The category defaults to being the same as the Integration name, but can be changed later via that API.  Changing the action category will not impact the action - integration relationship.

I would not expect changing the category to have any impact on existing published flows.

To actually move an action to a different integration then you could use the import / export in the UI to do it, or it could be done via "CX as Code" if you wanted a automated approach. These sorts of changes would require flows to be updated to use the new actions.

Hello,

We have a requirement to change the Integration/ Category on DataActions. We have observed that there is API

'patch /api/v2/integrations/actions/{actionId}' which allows to enter the Category to patch with the action. Would like to know if this would work updating the Integration associated to the DataAction and if so, are there any negative impacts of using this API and once Action is updated, do we need to republish the Architect Flows using the updated DataActions?

Hello Jason,

Thank you for the update. I would like to change the Integration itself and obviously category by changing the integration. We understood there is a limitation on how many Genesys DataAction Integrations that can exist in the system. To avoid the limitation, we are trying to merge few of the existing integrations into one and want to change the Integration on the already created DataActions. I thought changing category would change the Integration associated to the DataAction, so that we can remove some of the existing Integrations after moving Actions.

Let me know if there is a way to achieve it.

The category defaults to being the same as the Integration name, but can be changed later via that API.  Changing the action category will not impact the action - integration relationship.

I would not expect changing the category to have any impact on existing published flows.

To actually move an action to a different integration then you could use the import / export in the UI to do it, or it could be done via "CX as Code" if you wanted a automated approach. These sorts of changes would require flows to be updated to use the new actions.

Hello,

We have a requirement to change the Integration/ Category on DataActions. We have observed that there is API

'patch /api/v2/integrations/actions/{actionId}' which allows to enter the Category to patch with the action. Would like to know if this would work updating the Integration associated to the DataAction and if so, are there any negative impacts of using this API and once Action is updated, do we need to republish the Architect Flows using the updated DataActions?

There is a limit of 50 Web Service Data Action Integrations and an overall limit of something like 200 integrations.

To move your actions around the typical options are Import / Export from the UI or automating your configuration changes via CX as Code.

Hello Jason,

Thank you for the update. I would like to change the Integration itself and obviously category by changing the integration. We understood there is a limitation on how many Genesys DataAction Integrations that can exist in the system. To avoid the limitation, we are trying to merge few of the existing integrations into one and want to change the Integration on the already created DataActions. I thought changing category would change the Integration associated to the DataAction, so that we can remove some of the existing Integrations after moving Actions.

Let me know if there is a way to achieve it.

The category defaults to being the same as the Integration name, but can be changed later via that API.  Changing the action category will not impact the action - integration relationship.

I would not expect changing the category to have any impact on existing published flows.

To actually move an action to a different integration then you could use the import / export in the UI to do it, or it could be done via "CX as Code" if you wanted a automated approach. These sorts of changes would require flows to be updated to use the new actions.

Hello,

We have a requirement to change the Integration/ Category on DataActions. We have observed that there is API

'patch /api/v2/integrations/actions/{actionId}' which allows to enter the Category to patch with the action. Would like to know if this would work updating the Integration associated to the DataAction and if so, are there any negative impacts of using this API and once Action is updated, do we need to republish the Architect Flows using the updated DataActions?

Can you explain 'Automating your configuration changes via CX as Code'?

There is a limit of 50 Web Service Data Action Integrations and an overall limit of something like 200 integrations.

To move your actions around the typical options are Import / Export from the UI or automating your configuration changes via CX as Code.

Hello Jason,

Thank you for the update. I would like to change the Integration itself and obviously category by changing the integration. We understood there is a limitation on how many Genesys DataAction Integrations that can exist in the system. To avoid the limitation, we are trying to merge few of the existing integrations into one and want to change the Integration on the already created DataActions. I thought changing category would change the Integration associated to the DataAction, so that we can remove some of the existing Integrations after moving Actions.

Let me know if there is a way to achieve it.

The category defaults to being the same as the Integration name, but can be changed later via that API.  Changing the action category will not impact the action - integration relationship.

I would not expect changing the category to have any impact on existing published flows.

To actually move an action to a different integration then you could use the import / export in the UI to do it, or it could be done via "CX as Code" if you wanted a automated approach. These sorts of changes would require flows to be updated to use the new actions.

Hello,

We have a requirement to change the Integration/ Category on DataActions. We have observed that there is API

'patch /api/v2/integrations/actions/{actionId}' which allows to enter the Category to patch with the action. Would like to know if this would work updating the Integration associated to the DataAction and if so, are there any negative impacts of using this API and once Action is updated, do we need to republish the Architect Flows using the updated DataActions?

Moving to CX as Code is a big topic.  Here is an into to using it:

https://developer.genesys.cloud/devapps/cx-as-code/

It probably wouldn't save you time to use CX as Code to perform this migration, but long term having your configuration management done via "code" provides a bunch of advantages. So, you could potentially use this project as a way to see what CX as Code is all about.

If this is something you need to get done today, then the export and import capabilities of the UI is probably the fastest solution.

Can you explain 'Automating your configuration changes via CX as Code'?

There is a limit of 50 Web Service Data Action Integrations and an overall limit of something like 200 integrations.

To move your actions around the typical options are Import / Export from the UI or automating your configuration changes via CX as Code.

Hello Jason,

Thank you for the update. I would like to change the Integration itself and obviously category by changing the integration. We understood there is a limitation on how many Genesys DataAction Integrations that can exist in the system. To avoid the limitation, we are trying to merge few of the existing integrations into one and want to change the Integration on the already created DataActions. I thought changing category would change the Integration associated to the DataAction, so that we can remove some of the existing Integrations after moving Actions.

Let me know if there is a way to achieve it.

The category defaults to being the same as the Integration name, but can be changed later via that API.  Changing the action category will not impact the action - integration relationship.

I would not expect changing the category to have any impact on existing published flows.

To actually move an action to a different integration then you could use the import / export in the UI to do it, or it could be done via "CX as Code" if you wanted a automated approach. These sorts of changes would require flows to be updated to use the new actions.

Hello,

We have a requirement to change the Integration/ Category on DataActions. We have observed that there is API

'patch /api/v2/integrations/actions/{actionId}' which allows to enter the Category to patch with the action. Would like to know if this would work updating the Integration associated to the DataAction and if so, are there any negative impacts of using this API and once Action is updated, do we need to republish the Architect Flows using the updated DataActions?

There is a limit of 50 Web Service Data Action Integrations and an overall limit of something like 200 integrations.

To move your actions around the typical options are Import / Export from the UI or automating your configuration changes via CX as Code.

Hello Jason,

Thank you for the update. I would like to change the Integration itself and obviously category by changing the integration. We understood there is a limitation on how many Genesys DataAction Integrations that can exist in the system. To avoid the limitation, we are trying to merge few of the existing integrations into one and want to change the Integration on the already created DataActions. I thought changing category would change the Integration associated to the DataAction, so that we can remove some of the existing Integrations after moving Actions.

Let me know if there is a way to achieve it.

The category defaults to being the same as the Integration name, but can be changed later via that API.  Changing the action category will not impact the action - integration relationship.

I would not expect changing the category to have any impact on existing published flows.

To actually move an action to a different integration then you could use the import / export in the UI to do it, or it could be done via "CX as Code" if you wanted a automated approach. These sorts of changes would require flows to be updated to use the new actions.

Hello,

We have a requirement to change the Integration/ Category on DataActions. We have observed that there is API

'patch /api/v2/integrations/actions/{actionId}' which allows to enter the Category to patch with the action. Would like to know if this would work updating the Integration associated to the DataAction and if so, are there any negative impacts of using this API and once Action is updated, do we need to republish the Architect Flows using the updated DataActions?

Genesys Cloud Functions limit for Integrations is only 10. Is there an option to increase this limit?

There is a limit of 50 Web Service Data Action Integrations and an overall limit of something like 200 integrations.

To move your actions around the typical options are Import / Export from the UI or automating your configuration changes via CX as Code.

Hello Jason,

Thank you for the update. I would like to change the Integration itself and obviously category by changing the integration. We understood there is a limitation on how many Genesys DataAction Integrations that can exist in the system. To avoid the limitation, we are trying to merge few of the existing integrations into one and want to change the Integration on the already created DataActions. I thought changing category would change the Integration associated to the DataAction, so that we can remove some of the existing Integrations after moving Actions.

Let me know if there is a way to achieve it.

The category defaults to being the same as the Integration name, but can be changed later via that API.  Changing the action category will not impact the action - integration relationship.

I would not expect changing the category to have any impact on existing published flows.

To actually move an action to a different integration then you could use the import / export in the UI to do it, or it could be done via "CX as Code" if you wanted a automated approach. These sorts of changes would require flows to be updated to use the new actions.

Hello,

We have a requirement to change the Integration/ Category on DataActions. We have observed that there is API

'patch /api/v2/integrations/actions/{actionId}' which allows to enter the Category to patch with the action. Would like to know if this would work updating the Integration associated to the DataAction and if so, are there any negative impacts of using this API and once Action is updated, do we need to republish the Architect Flows using the updated DataActions?

Sesha,

What's the use case where you're needing more than 10 Functions integrations?  It's certainly something that we could consider, but I'd like to understand the rationale a little better before we start investigating.  

Also, to expand on the previous discussion, Data Actions are anchored to the integration at the time they are created. Much of this has to do with the fact that we support named integrations within Data Actions (Salesforce, Zendesk, Genesys Cloud, Etc.), where the authentication process is generally "baked in" to the concept of the action, so allowing you to programmatically "move" an action from one integration to another doesn't make a ton of sense.  

As Jason mentioned, you could use the UI (or the API) to copy the configuration of your action from the existing one into a new one that is under a different integration.  In the UI, this would use the "export" button to download a JSON file, which you can then use with the "import" button to create your new action.  In the API, this would simply be a GET of your existing action, and you would tweak the response from that to do the POST to create a new action with the new integration ID (this would be the same basic process CX as Code performs).  The follow on to this is that the "moved" action has a new ID, so you would need to update your call flows regardless of the methodology you use.  

Genesys Cloud Functions limit for Integrations is only 10. Is there an option to increase this limit?

There is a limit of 50 Web Service Data Action Integrations and an overall limit of something like 200 integrations.

To move your actions around the typical options are Import / Export from the UI or automating your configuration changes via CX as Code.

Hello Jason,

Thank you for the update. I would like to change the Integration itself and obviously category by changing the integration. We understood there is a limitation on how many Genesys DataAction Integrations that can exist in the system. To avoid the limitation, we are trying to merge few of the existing integrations into one and want to change the Integration on the already created DataActions. I thought changing category would change the Integration associated to the DataAction, so that we can remove some of the existing Integrations after moving Actions.

Let me know if there is a way to achieve it.

The category defaults to being the same as the Integration name, but can be changed later via that API.  Changing the action category will not impact the action - integration relationship.

I would not expect changing the category to have any impact on existing published flows.

To actually move an action to a different integration then you could use the import / export in the UI to do it, or it could be done via "CX as Code" if you wanted a automated approach. These sorts of changes would require flows to be updated to use the new actions.

Hello,

We have a requirement to change the Integration/ Category on DataActions. We have observed that there is API

'patch /api/v2/integrations/actions/{actionId}' which allows to enter the Category to patch with the action. Would like to know if this would work updating the Integration associated to the DataAction and if so, are there any negative impacts of using this API and once Action is updated, do we need to republish the Architect Flows using the updated DataActions?