With Shared Elements, application administrators can easily designate repeatable elements as a shared asset.
Unqork accelerates custom enterprise software development. A big part of this speed stems from the fact that repeatable elements and configurable components can be easily drag-and-dropped into multiple instances across different applications—without writing a single line of code.
However, with this repeatability comes the potential for complications—particularly in a highly-collaborative environment. If a communally-available element is, for example, edited at a fundamental level to adapt to the needs of one application, it may end-up causing conflict in a different application or instance. Unqork’s recently released Shared Elements feature solves this problem.
Enhanced Management of Shared Resources
With Shared Elements, application administrators can designate certain repeatable elements as shared (e.g., an organization may want to use the same log-in module or website header across all applications).
This designation lets all users (or “Creators” as we call them) know that this element is being used across multiple applications. With this knowledge, Creators can choose to “localize” the element if they need to make any changes to address specific challenges without the fear that they may impact any other instances.
Furthermore, the Shared Elements function will list all instances in which a repeatable element is used. This is crucial because if any changes to these shared elements are made (by Creators with the proper permissions), it will let them know they need to check and QA every instance in which that element appears.
With Shared Elements, organizations can continue to deploy faster, while still maintaining control over repeatable elements that appear in multiple instances throughout an application.