[MNT-19888] Export/import function for tenant process model references ex. Alfresco Repositories, Endpoints Created: 02-Aug-18  Updated: 02-Dec-19

Status: Need Info
Project: Service Packs and Hot Fixes
Component/s: APS Kickstart/Studio
Affects Version/s: Alfresco Activiti 1.5.1, Alfresco Process Services 1.9
Fix Version/s: None

Type: Feature
Reporter: Jennie Soria [X] (Inactive) Assignee: Mark Howarth
Resolution: Unresolved Votes: 0
Labels: London, Modeler-Publish
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File example1.5tenantConfig.png    
Issue Links:
Related
relates to ACTIVITI-998 Introduce Bootstrap mechanism to load... Open
is related to by ACTIVITI-998 Introduce Bootstrap mechanism to load... Open
Requires
requires ACTIVITI-799 "Redeploy app to another cluster" via... Open
Shadow
shadowed by ACTIVITI-457 Export/import function for tenant pro... Open
ACT Numbers:

00807289, 00969737, 00969735


 Description   

Summary

Any assets that are defined under the tenant in the IDM are not exportable with the export/import of an APP and the processes which may use those configured resources. You must manually set these resources in the destination environment making sure their name/id matches the reference used in the process that is dependent on it.

The following configurations needs easier method for export import for a tenant that would be referenced in process models would be:

  • Alfresco Repositories
  • Endpoints (endpoints, basic auths)
  • Data sources
  • Doc Templates
  • Email Templates
  • Logo

Ideally,

  • The ability to edit the file export to update any environment specific properties values (ex. endpoint url) for any item exported prior to import
  • The ability to select on export which configurations to export
    ex. check box select on export popup which items to export: all, repos, endpoints, datasources, doc templates, email templates
    ex. or make separate import files for each config group
  • The ability on import to choose which configs to import: all, repos, endpoints, datasources, doc templates, email templates
  • Import should prevent overwrites and conflicts, default fail with warning

Better yet

  • On export of an APP, process, form, datatable, etc... a list of or export of all referenced items from tenant config that are used in by the object be included in the resulting export and imported with the uplaod of app/model/form/stencil any object out of kickstart that references any tenant configuration item be handled.

Business Reason

Currently you need to login to destination environment and add the endpoints, templates etc... manually that are identically named as the referenced in models from source environment prior to publish/deployment of the application and its process models it uses. This can be quite problematic if you have copious endpoints defined and basic auths, templates etc....



 Comments   
Comment by Mark Howarth [ 23-Aug-19 ]

Reassigning to Doug Gruber, new APS PM.

Comment by Mark Howarth [ 02-Dec-19 ]

Assigning to Mark Howarth as PM for APS.

Generated at Fri Jul 10 05:12:59 BST 2020 using JIRA 7.6.3#76005-sha1:8a4e38d34af948780dbf52044e7aafb13a7cae58.