US 12,468,509 B2
Reusable entity modeling systems and methods
Dana Lawrence Khoy, Westford, MA (US); Albertus Hendrik Roos, Waterloo (CA); Richard Winfield Bolling, Hollis, NH (US); Renatus Cornelis Prins, Putten (NL); and Cheranthian Muthuvinayagam, Bedford, NH (US)
Assigned to OPEN TEXT SA ULC, Halifax (CA)
Filed by Open Text SA ULC, Halifax (CA)
Filed on May 4, 2017, as Appl. No. 15/587,014.
Claims priority of provisional application 62/331,797, filed on May 4, 2016.
Claims priority of provisional application 62/331,785, filed on May 4, 2016.
Prior Publication US 2017/0322716 A1, Nov. 9, 2017
Int. Cl. G06F 8/35 (2018.01); G06F 3/0482 (2013.01); G06F 3/04847 (2022.01); G06F 8/34 (2018.01); G06F 8/36 (2018.01); G06F 8/60 (2018.01); G06F 16/22 (2019.01); G06F 30/20 (2020.01)
CPC G06F 8/35 (2013.01) [G06F 3/0482 (2013.01); G06F 3/04847 (2013.01); G06F 8/34 (2013.01); G06F 8/36 (2013.01); G06F 16/22 (2019.01); G06F 30/20 (2020.01); G06F 8/60 (2013.01)] 15 Claims
OG exemplary drawing
 
1. An entity modeling system, comprising:
a processor;
a non-transitory computer readable medium; and
instructions stored on the non-transitory computer readable medium and translatable by the processor to perform:
receiving, from a user device, an instruction to create a new entity model, the entity modeling system operating on an application development platform;
importing an application package into a design time environment on the application development platform, wherein the application package contains:
a previously generated entity model, the previously generated entity model defining a first process application for a first problem domain, wherein the first process application is modeled via the previously generated entity model as a set of entities that are linked with each other by relationships that specify dependencies and requirements among the set of entities;
a design-time application programming interface (API) of the previously generated entity model; and
an entity model specification of the previously generated entity model, wherein the entity model specification prescribes interface specifications for the set of entities, includes worklists, forms, and, for every property of a respective entity, a property name and an associated data type;
wherein each respective entity of the set of entities is composed from a set of entity building blocks, the set of entity building blocks having element types in an application architecture based on which the application development platform is built, the set of entity building blocks including an entity building block that defines a characteristic for the respective entity and that comprises code instantiated from a special element class to implement settings for the respective entity, wherein the special element class defines the entity building block as having a structural, decorative, or functional element type; and
responsive to an instruction from the user device, making a change to at least one of the settings so as to modify the entity building block, wherein modifying the entity building block changes the characteristic for the respective entity and, as such, customizes the new entity model for defining a second process application for a second problem domain;
wherein the entity modeling system stores customization information relating to the change independently of the second process application, and wherein the entity modeling system applies the customization information to the second process application after the second process application is packaged and deployed.