By expanding “Form data”, you can start configuring the procedure. The image displayed is as follows:
Image 1: initial screen of the “own forms” management environment, with its 5 sections to fill out.
Form data requires filling in the following elements:
a) Unique identifier : will be used for the form access URL
For example, https://seu-e.cat/tramits/7996100001/exemple-formulari
⚠️IMPORTANT: Once the procedure has been created, this identifier cannot be modified. Therefore, if you want to reuse the procedure, it is important not to enter information that could change in the identifier name (e.g. 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 into the "subject" of registration, so a format such as the following "Call for an A1 archivist position (INT 3125)" may be interesting, where the code can be used to help you classify in a more agile way.
c) Procedure code : this is the specific code that will appear in the XML.
The procedure editor must indicate a 4-digit numerical value (taking into account that if a 1, 2 or 3-digit number is added, zeros will be added in front. 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 procedure that travels?
To build the code that arrives in the XML, a nomenclature has been established so that the field is numeric and unique within the database:
- concatenate the 4-digit number entered by the user
- add a "9" at the front (so that the leading 0s are not removed when saving) and the entity's INE10 code at the end.
Therefore, the final format when capturing it within the XML will be:
9+[Indicated 4-digit value]+INE10 code.
For example, for code 1234 and INE10 code of Training Entity A (7996100001), the procedure code would be 912347996100001.
This value will be reported in the <codiTramit> field of the XML as can be seen below:
Image 2: screen of the configuration of the own procedure, and view in XML
d) Description : refers to a brief description of the procedure. This corresponds to a brief text that describes the procedure and that will appear below the processing form.
e) Form type : 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 extend functionalities. In this field, therefore, nothing needs to be done.