Clients to be able to Build reusable Content to be embedded in other Apps/Forms

[gtwr1970]

Ascensus:

Customer Problem:

Today Clients cannot reuse content across Projects. They have to re-create the sections that are common across their Apps/Forms. For e.g. it is like that most of their Apps/ Forms will have a Address Section or a Customer Details Section . Today they have to manually recreate this in each of their Apps.

Scope:

• Clients should be able to create a section once and reuse that across their Apps/Forms.

• Data sources that are part of the section that is getting reused - will become part of the Project which invokes the reusable section

• Should we consider a different Project Type ?

• Where will Clients create the reusable Section ?

• Can the designers make changes to the section after embedding it in their project ?

• Can we have 2 types

  • One where Designers can make changes ( to the section) after embedding the reusable section in their project - > Injecting the section along with Data sources at Design Time

  • The Other is where Designers cannot make any changes to the section they are embedding in their project. And Any change made to the section will have to propagated to all the Projects embedding it -> Injecting the section along with Data Sources at run time.

High Level solution :

• We will have a new Project type called 'Module'

• The Designer will also have to specify - in what kind of projects the module can be consumed - Forms, Apps , Any ( meaning module can be consumed in both forms and apps)

• Modules will not be multipage

• Modules can be embedded in Projects in 2 ways -

  • Design time ( unlinking the module when embedding)

  • Run time Injection ( keeping the link between the project and module intact)

• When we make changes and publish a module - We should let the users know the list of projects that would be impacted ( so all projects that have embedded the module and did not unlink the module)

• What should be the actions available to designer when creating the modules - Need to groomed for each type of module

• Data Sources behavior - when modules are unlinked - then data sources of the module are available to the Project that they are embedded into . If the module remains linked - then the Project that embeds the module does not have access to it's data sources.

• i18n & Localization - not applicable for Reusable content ? - Needs discussion to confirm

• Global Styles - should be available

• Data Tables - not available . But button actions to do look up should be made available within modules ( that can be consumed in Apps)

Use Cases:

Lot of forms and apps have set of data replicated in multiple screens within a project / and across projects