Add mapping Apps & Machine attribute on App import

Product Suggestions
1

Here’s the corrected version of your email, with improved phrasing and grammar:

Hi,

We have two instances (DEV and PROD), and when we export an app from DEV to PROD, all apps become “corrupted” because we need to manually reconnect the dots (update all transitions between apps and triggers that use machine attributes).

I suggest adding a step in the import process where:

  • All machine attributes from the imported app are listed, and the user selects which local instance machine attributes will be mapped (similar to importing a CSV file into a table). This mapping will be saved so that the next import automatically proposes the previously saved mapping.
  • All transitions between apps will be proposed in the same manner as the machine attribute mapping.
  • A “skip” button can be added, so if no mapping is defined by the user, the app will be imported as per the current process.

For apps with links and machine attributes, manually reconnecting everything is so time-consuming that it significantly impacts our bug-fixing and enhancement delivery timelines.

Regards,

2

Hey @thomas.riehl -

We are nearing the completion of some big improvements to import export to remove the need to do as much manual work when moving app that rely on machines. With this new implementation machines, machine types, machine states, attributes, etc will all be brought on export/import. We will still allow each machine to be mapped to unique opc ua/mqtt nodes in dev/prod, but the types, machines, downtime reasons, etc will be transfered. This will make it so your apps do not need a reconnecting of the wires for machines.

Along with these improvements will will be a number of smaller improvements to how import and export is handled for other components of apps. This will be rolling out later this fall, it is in the final stages of engineering now.

Pete

1 Like