By displaying "Form data", you can start the configuration of the procedure. The displayed image is as follows:
Image 1: initial screen of the "own forms" management environment, with its 5 sections to fill in.
Form data requires filling in the following elements:
a) Unique identifier : will be used for the access URL to the form
For example, https://seu-e.cat/tramits/7996100001/exemple-formulari
⚠️IMPORTANT: once the procedure has been created, this identifier cannot be modified. Therefore, it is important that if you want to reuse the procedure, you do not enter information that could change in the identifier name (eg years).
b) Procedure name : name that we specifically want to give to the procedure. For example: Call for an A1 archivist position
🗨️NOTE: in the event that you are interested in classifying the procedure internally, this field will go to the "subject" of registration, so a format like the following may be interesting "Call for an A1 archivist position (INT 3125)”, where the code can be used to help you sort more quickly.
c) Code of the procedure : it is the specific code that will appear in the XML.
The procedure editor must indicate a 4-digit numerical value (note that if a 1, 2 or 3-digit number is added, zeroes will be added in front of it. Therefore, it will always be 4 digits) .
🗨️NOTE: What if what I want is to be able to use this code to integrate it into my systems from the XML of the own procedure that travels?
To build the code that reaches the XML, a nomenclature has been established so that the field is numeric and unique within the DBDD:
- concatenate the 4-digit number entered by the user
- add a "9" in front (so that the 0 in front is not removed when saving) and the INE10 code of the entity at the end.
So the final format at the time of capturing it into the XML will be:
9+[Indicated 4-digit value]+INE10 code.
For example, for code 1234 and INE10 code of Training Institution A (7996100001), the procedure code would be 912347996100001.
This value will be reported in the <Process code> field of the XML as can be seen below:
Image 2: screen of the configuration of the own procedure, and view in the XML
d) Description : refers to a brief description of the procedure. It corresponds to a short text that describes the procedure and that will appear under the processing form.
e) Type of form : at the moment it is a fixed field that can only be Generic Instance. In the future it is planned to offer more starting models that can expand functionalities. In this field, therefore, nothing needs to be done.