Fusion to generate a random ref id | Community
Skip to main content
A
amazingjameso
Level 2
November 1, 2024
Question

Fusion to generate a random ref id

  • November 1, 2024
  • 2 replies
  • 967 views

Is there a way to have fusion generate a unique/random reference id for let's say a document, so when formatted ex. " CL <refid> MMYYY " can be used to track documents or used in a custom dropdown field in WF without having to use the doc id thats in the URL by default? almost like how a project has it's own refid associated to it.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.

2 replies

ChristinaJay
ChristinaJay
Level 4
November 1, 2024

We use something like that in a calculated field not necessary fusion. But it provides a tracking # - usually the project ref, followed by the focus, followed by the  document ref.

 

So, something like this - 1173799-RET-1173800

    A
    amazingjamesoAuthor
    Level 2
    November 1, 2024

    Thanks! our acceptance criteria shows:

     

    1. REF ID Generation:
      • Fusion generates a unique REF ID for each new claim when the Auth Approver approved the associated proof content, which is used in the Claim ID format CL<REF ID>MMYYYY.
    1. Repository Creation and Management:
      • Fusion pulls claims from the request queue and organizes them into a new project within an overarching "Claims Repository" project.
      • Each new claim is added to the request queue of the new project.
      • The overarching "Claims Repository" project manages all claims, providing a centralized view.
    1. Claim Reference Management:
      • Fusion updates the "Existing Claim Reference" dropdown on the FIM submission form & the Claims Repository project with valid claims.
      • Claims older than one year are automatically removed from the dropdown.

    So i'm thinking if we can use a calculated field to generate a ref id then we can have fusion do the rest of this and pull in that id and use it where we need to? The claim could be a pdf, word doc, that's a proof and when approved gets a unique id, would a calculated field be able to do this? i do know that every doc has it's own id in the url and we could use that as a last resort, but it's long, were looking to see if fusion can create a smaller unique number to track, but i'm aiming at no, but thought i'd ask

    Sven-iX
    Community Advisor
    Sven-iXCommunity Advisor
    Community Advisor
    November 1, 2024

    Hi @amazingjameso 

     

    So Fusion doesn't generate what you need: a unique "index" or reference. 

    Workfront does generate a referenceID on each object - you could concatenate that plus e.g. timestamp of entryDate - that ought to be fairly unique? 

    S
    ScottMo1
    Level 4
    November 1, 2024

    We use fusion to generate various ID#s that give us a smart number so we know which Project the issue was generated.  

     

    We create ID#s on issues.  It is a custom field that we use fusion to write to it.   Every time a new issue is created it will kick off the fusion scenario.   We have a "hard code" identifier (for example SHIP- ) then the counter is added after the dash.  We know this is a SHIP- issue.     With the use of the DataStore and keys with in fusion, each time a issue is created that matches one of our projects the counter will increment by 1 and append the "Hard Code" and the incremental number to the issue in our custom field.   We can also set the counter to start with any number sequence we would like.  

     

    The fusion scenario works likes this:

     

    Watch event for a new issue --> filter out the Projects we are watching for to append the number --> go to the Data Store and grab the current number matching the project ID --> Update Record (place that Hard Code and number in the custom field --> then update the Data Store by incrementing by 1 so it is ready for the next call.

     

    Let me know if you want to know more and we can chat offline.

      Terms & ConditionsAccessibility statement

      Loading footer...