Missing files in published scoped application

Fredrik Larsso1
Mega Expert

‎05-14-2019 06:39 AM

Hi,

I have a issue regarding flows and flows action in a scoped application.

When I publish to customer repository, and then tries to install in test or production, a lot of files is missing. And I can't open the flow, I get an error saying "Action type definition with Id <sys_id> is missing"

Anyone else that have this issue? It works if i move the files manually within a update set.

I have tried building it in my personal dev instance, and publish to local updateset and it will still misses a lot of files.

Labels:
  • 2,943 Views
2 REPLIES 2

David280
Tera Contributor

‎10-21-2019 05:48 AM

I have exactly the same issue. When I have installed the scoped application in test from dev i get an error saying  "Action type definition with Id <sys_id> is missing" because I have a sub flow with in a Flow. The subflow can not be accessed and when I try to open it from flow designer view (within parent flow) a popup shows the same error message.

I have reverted all "skipped" in system upgrade log from when the updated application was installed. 

Have you got any input to this issue?

I only found a known error with the short workaround below:

Workaround

Develop all new workflows in the global domain and move any existing scoped workflows also to the global domain.

0 Helpfuls

Dorian11
Tera Contributor

‎02-25-2020 08:14 PM

The reason this is happening could be because the subflow calls something in either another application or IntegrationHub that isn't installed in the test or production envrionment.

 

For example:

Scenario: Dev environment, in your scoped app. Turned on IntegrationHub through HI. Test environment doesn't have your app and doesn't have IntegationHub turned on.

1. create a subflow that sends a message to slack webhooks. Save it in your application. Publish internally. Install in test, you will get the error you have.

Scenario: Dev environment, in your scoped app. Turned on IntegrationHub through HI. Test environment doesn't have your app and you have IntegrationHub turned on.

1. create a subflow that sends a message to slack webhooks. Save it in your application. Publish internally. Install in test, your subflow will work 🙂

 

The same thing will happen if you call something from a scoped application you don't have installed. Hope this helps you and others. The workaround of putting flows in global would work as well, but probably not the best model to follow. 

 

Cheers,

Dorian

0 Helpfuls