First of all, after the brief introduction, we have to know about the different environments that can be found in Unifier:
uStage and uDesigner: these will form up the development environment. uDesigner is the module where everything is designed (what a complex and impossible to understand name they chose. Always trying to fool us!): fields of the forms, forms, workflows, BPs, custom modules, etc. uStage is a very versatile Unifier environment that admits a lot of changes impossible to be done in production.
Unifier: main environment that gives the name to the application. It can be splitted into two. There can be two Unifiers, the test and the production environments. The main difference between uStage and Unifier is the availability of uDesigner. You will find it blocked if u access it from a Unifier environment.
Once introduced to the different instances of Unifier, the one that I will use all over the posts is Development (uDesigner and uStage). This has two reasons of being like that: privacy for the project/company I’m working for and the possibility of using fake data to create numerous examples.
It is really important to be aware of the implications of a migration from uStage to Unifier. In our terminology it is called “Publish”. We have to think twice before taking this step. After publishing something, none of it’s elements will be ever able to be removed. After learning how to use the different functionalities of uDesigner, you will be capable of hiding them, but they will be always present in the database tables.