Application-extending for new user population

To support a new user population within an existing database, run the New Application wizard to generate an application that extends the classes of the existing application’s case types. Then use the ruleset override pattern to specialize the existing application.

By using this specialization, a new class group is created for the new user population, plus case data will be stored in separate tables. 

Suppose there is a requirement for a new user population to handle Online Streaming events. Create a new application, Online Streaming Event, by extending the Booking application.

Assignment and attachment instances cannot be separated into different tables based on application. We can leverage the below Organization properties to restrict access between these applications. 

Suppose the new user population is associated with the new division and this new user population should not access any assignments created in the original division. The easiest solution is to implement a Read Access Policy in the Work- class that references the following Access Policy Condition. 

Ruleset specialization within new applications built on the existing application would suffice to support a new user population, provided the new user population is hosted within a new database.

For example: Suppose there is a requirement for a new user population to handle Online Music events. Create a new application Online Music Event by extending the Booking application. Host that new Online Music events application within a new database.