This documentation refers to the new process editor of the platform. If you are using the current process editor, access Configure activity. 

The rules for attachments are not mandatory in any component. They can or cannot be defined according to the specific needs of each stage, process, or business.

If no rule is defined, it is allowed to add any type and any quantity of attachments, meaning that no validation is performed.

Click here to learn how to configure rules for attachments in a stage of the process.

→ The attachment must be equal to 2.

It is mandatory to add two attachments at this step, and adding more is not allowed.

→ The attachment must be greater than 0.

It is mandatory to add at least one attachment at this step, and adding more than one is allowed.

→ The attachment must be greater than or equal to 1.

It is mandatory to add at least one attachment at this step, and adding more than one is allowed.

→ The attachment must be less than 3.

It is allowed to add up to two attachments at this step or leave the step without attachments.

→ The attachment must be less than or equal to 4.

It is allowed to add up to four attachments at this step or leave the step without attachments.

→ The attachment must be any one.

It is allowed to add any type and any quantity of attachments at this step, including leaving the step without attachments.

In a process of Request for hour exemption due to medical issues for the Payroll area, the requester must necessarily submit the medical certificate that justifies the exemption. The certificate is accepted in any format, which can be an image, a photo, a PDF document, a ZIP file, in short, no requirements are made regarding the type of file. However, only one certificate is allowed to be submitted per request, meaning that if the requester has more than one certificate, they must open a request for each one.

Thus, the rule can be defined as follows:

→ The attachment must equal 1.

It is mandatory to add one attachment of any type. And it is not allowed to add more than one.

In a process of Simple budget approval, the person responsible for the approval prefers that the details be provided directly in the request form, so that when opening the request for analysis, the amount to be approved is already evident, without the need to open a document to see the information.

→ In this case, it is not necessary to add any rules, just activate the option Prohibit attachments, which means that no attachments are allowed at this stage. The budget details must be added in the request form.

→ The attachment must be equal to 1 with the file name containing the term note at the beginning.

It is mandatory to add an attachment that has the term note at the beginning of its name.

→ The attachment must be less than or equal to 2 with the extension equal to .zip.

It is allowed to add up to two attachments with the .zip extension or leave the step without attachments.

→ The attachment must be equal to 1 with the name and extension containing the term boleto at the beginning and the term .pdf at the end.

It is mandatory to add an attachment that has the term boleto at the beginning of its name and that is a PDF document.

In a ticket opening process for the IT department, the requester needs to send at least one image of the inconsistency that is occurring or of the resource for which they are requesting assistance. Only images of the PNG type are accepted. If possible, it is also interesting to send the log, but it must be in TXT format and is not mandatory.

Thus, the rules can be defined as follows:

→ The attachment must be greater than or equal to 1 with the extension equal to .png.

It is mandatory to add at least one attachment that is an image with the .png extension. However, if the requester wishes, they can add more attachments.

→ The attachment must be greater than or equal to 0 with the extension equal to .txt.

If the requester can obtain the log, they can attach it to the request to facilitate analysis. However, it is not mandatory to attach it.

→ The attachment must be equal to 0 with the extension equal to .exe.

For security reasons, it is not allowed to add any attachment that has the .exe extension.

In a payment request process for the Finance area, the requester must submit three documents: the electronic invoice, the payment slip, and a detailed list of the products or services acquired. The documents must be in PDF format and identified by the respective names "boleto", "fatura", and the invoice must be identified with the code "NF" at the beginning of the name.

Thus, the rules can be defined as follows:

→ The attachment must be equal to 1 with the name and extension containing the term boleto in the name and the term pdf in the extension.

It is mandatory to add an attachment that has the name boleto and is a document with the .pdf extension.

→ The attachment must be equal to 1 with the name and extension containing the term fatura in the name and the term pdf in the extension.

It is mandatory to add an attachment that has the name fatura and is a document with the .pdf extension.

→ The attachment must be equal to 1 with the name and extension containing the term NF at the beginning of the name and the term pdf at the end of the extension.

It is mandatory to add an attachment with the characters NF at the beginning of its name and with the .pdf extension to identify it as the invoice. Attachments such as NF_10355.pdf, NF89665.doc.pdf, NF-58361.pdf would be accepted.

→ The attachment must be equal to 1 with advanced condition fatura.pdf|nota.pdf.

It is mandatory to add an attachment named fatura or nota with the .pdf extension. Adding more than one is not allowed.

→ The attachment must be any with advanced condition !server.*.

It is allowed to add any type of attachment with a name different from server and with any extension or leave the step without attachments. The name server is prohibited.

→ The attachment must be greater than or equal to 3 with advanced condition boleto.pdf.

It is mandatory to add at least 3 attachments, and more can be added, that contain the term boleto in the name and with the .pdf extension.

In a Travel Reimbursement Request process for the Finance area, the requester can submit proof of payment for the stay, transportation, and ticket if the trip was for an event. The proofs need to be in PDF and identified by name.

Thus, the rules can be defined as follows:

→ The attachment must be greater than or equal to 1 with advanced condition estadia.pdf|transporte.pdf|ingresso.pdf.

It is mandatory to add at least one attachment, and more can be attached, that contains the term estadia, transporte, or ingresso in the name and with the .pdf extension.

In a Request for Office Supplies process for the Purchasing area, the requester needs to submit a photo of the requested material to serve as a reference and facilitate the purchase. This photo can be of various types.

Thus, the rules can be defined as follows:

→ The attachment must be greater than or equal to 1 with advanced condition .png|.jpg|.jpeg|.bmp.

It is mandatory to add at least 1 attachment with any name that is an image with one of the allowed extensions: .png, .jpg, .jpeg, or .bmp.

<script>
    (function() {
        function toggleAreas(isExpand, $parent) {
            var $items = $parent.find('.panel');

            $.each($items, function(idx, el) {
                var $arrow = $(el).find('span.cloakToggle').find('span');
                var $content = $(el).find('span.cloak');
                if (isExpand) {
                    $arrow.removeClass('cloakDefaultOpen').addClass('cloakDefaultClose');
                    $content.show();
                } else {
                    $arrow.addClass('cloakDefaultOpen').removeClass('cloakDefaultClose');
                    $content.hide();
                }
            });
        }

        $(document).on('click', '#toggleAll-1', function(ev) {
            ev.preventDefault();
            var isExpand = $(this).data('expand');
            var $parent = $(this).nextAll('.sectionColumnWrapper').first();
            toggleAreas(isExpand, $parent);
            $(this).data('expand', !isExpand);
        });
    })();
</script>
<a id="toggleAll-1" href="#" data-expand="true">Open/close all scenarios</a>

<script>
    (function() {
        function toggleAreas(isExpand, $parent) {
            var $items = $parent.find('.panel');

            $.each($items, function(idx, el) {
                var $arrow = $(el).find('span.cloakToggle').find('span');
                var $content = $(el).find('span.cloak');
                if (isExpand) {
                    $arrow.removeClass('cloakDefaultOpen').addClass('cloakDefaultClose');
                    $content.show();
                } else {
                    $arrow.addClass('cloakDefaultOpen').removeClass('cloakDefaultClose');
                    $content.hide();
                }
            });
        }

        $(document).on('click', '#toggleAll-2', function(ev) {
            ev.preventDefault();
            var isExpand = $(this).data('expand');
            var $parent = $(this).nextAll('.sectionColumnWrapper').first();
            toggleAreas(isExpand, $parent);
            $(this).data('expand', !isExpand);
        });
    })();
</script>
<a id="toggleAll-2" href="#" data-expand="true">Open/close all questions</a>

This documentation is valid from the Voyager update (2.0). If you are using a previous update, it may contain information different from what you see on your platform.

<style type="text/css">
.confluenceTable .confluenceTd {
    vertical-align: middle !important;
}
</style>

<!-- Hotjar Tracking Code for http://tdn.totvs.com/display/fb -->
<script>
    (function(h,o,t,j,a,r){
        h.hj=h.hj||function(){(h.hj.q=h.hj.q||[]).push(arguments)};
        h._hjSettings={hjid:1280165,hjsv:6};
        a=o.getElementsByTagName('head')[0];
        r=o.createElement('script');r.async=1;
        r.src=t+h._hjSettings.hjid+j+h._hjSettings.hjsv;
        a.appendChild(r);
    })(window,document,'https://static.hotjar.com/c/hotjar-','.js?sv=');
</script>