You are viewing limited content. For full access, please sign in.

Question

Question

Business process don´t create a single PDF

asked on June 21, 2021 Show version history

I created this business process to generate a label to be stuck in a file box.

In this process the 'content' field must accumulate the 'document name' values from all documents that have the same value for the '#box' field and the associated 'box tag'.

Next, a PDF document is filled with the values stored in the tokens

THE PROBLEM:
It turns out that it generates a PDF for each "content" token instead of creating a single PDF with all the values of the "content" field

Can you help me with this problem?

 

Down the workflow:

 

Create PDF Box Label:

Workflow Details:
Connection Profiles:

  •  INFODOCS (pc005; INFODOCS; wf)

Attachments:

  • label cx file.pdf

Corporate Process Options:
    • Can be booted on Laserfiche clients connected to 'INFODOCS'
    • Can be viewed on Laserfiche clients connected to 'INFODOCS'
    • Status started: Running
    • Status Completed: Completed
    • Status Canceled: Terminated

       

Try-Catch:
        Attempt { }
        Capture (Exception)

                Try Branch:
                

                        Assign Token:
                        Create the following tokens:
                        • %(year)
                        • %(box)
                        • %(Content) (multiple-value)
                        • %(Rate)

                        Search Repository:
                        Search Query:
                                ({LF:Tags="box"})
                        If a search is a shortcut, keep it as a shortcut
                        Not case sensitive. Sensitive to accent:
                        Return: All results
                        Additional properties:
                        Properties of field options:
                        Sorting properties:

                        For Each Entry:
                        Iterate through the entries in:
                        (Search Repository::Output Entries)

                                Find Entry:
                                Find the entry with the ID: %(ForEachEntry_CurrentEntry_ID)
                                Additional properties:
                                Properties of field options:

                                Retrieve Field Values:
                                Entry: (For Each Entry::Current Entry)
                                Field values ​​to retrieve:
                                • YEAR
                                • BOX
                                • CLASSIFICATION

                                Add Values:
                                Modify the following tokens:
                                • %(year) = %(RetrieveFieldValues_year)
                                • %(box) = %(RetrieveFieldValues_box)
                                • %(Content): Append %(ForEachEntry_CurrentEntry_Name) (multiple-value)

                                Assign Tags:
                                Entry: (For Each Entry::Current Entry)
                                Remove Tags: box

                        Create Entry:
                        Name: Box Label %(box)
                        Type: Document
                        Volume: <Use default volume from parent folder>
                        Destination: \new

                        Attach Electronic Document:
                        Attach cx arq tag to (Create Entry::OutputEntry)
                        Source: Server Attachment
                        If an electronic document already exists: Replace the electronic document and do not record a warning

 

                        Track Tokens:
                        Report the value of the following tokens:
                        • Content

 

                        Fill Out PDF Form:
                        PDF: (Create Entry::OutputEntry)
                        Master Form: cx file label
                        Merge field content with image
                        Fields to be filled:
                        • YEAR = %(RetrieveFieldValues_YEAR)
                        • Rating = %(RetrieveFieldValues_CLASSIFICATION)
                        • Cash = %(RetrieveFieldValues_CAIXA)
                        • CONTENT = %(Entry Name)

                Catch Branch:
                Capture (Exception)

        End Workflow:
        Complete current and primary workflows

 

 

 

 

The PDF document is this:

 

Where the "content" field should receive all "document name" values from the token  

 

0 0

Replies

replied on June 21, 2021

Do you have the original creation of the multi-value token outside of the try / catch?  If you are initially assigning the token within, maybe it is reassigning it and not adding the next value.  Just a thought.

1 0
replied on June 21, 2021

I will look ... thanks

0 0
replied on June 21, 2021

Your summary says: CONTENT = %(Entry Name) 

So the content field gets set to the name of the document that started this workflow. You want to set it to the Content token you created and format the token to show all values delimited by a new line.

1 0
replied on June 21, 2021 Show version history

Yes ... the content token must show all values (document name). For example ... in the box 2017 have 10 docs.

The token must capture the name of these 10 docs. (doc1, doc2, doc 3 etc)

0 0
replied on June 21, 2021

Right, I'm saying you've configured the activity wrong and it can get at most one name in there currently. You need to replace the %(Entry Name) token with the %(Content) one.

0 0
replied on June 21, 2021 Show version history

I was change ... but we don´t have success. The BP create 8 label. One for each doc 

I need one label doc (etiqueta cx 2017 doc) for the 8 LF docs  

 

0 0
replied on June 22, 2021

Your workflow only creates one document, so it's likely not the definition, but the starting rule.

It sounds like possibly your starting rule is detecting the document creation and triggering another instance of the same workflow. Try searching in the Workflow Designer for instances of this workflow and seeing if they have different starting entries. Or show us a screenshot of your starting rules.

1 0
replied on June 24, 2021

hi Miruna .. We solved this issue with this: 

In the PDF tokes ... we choose the "Token Dialog" and mark how show below

  

0 0
replied on June 24, 2021

Here is the result 

 

0 0
replied on June 24, 2021

Thanks for all

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.