Adobe Workfront Experts on Workfront Fusion

This is a great question to get the thread started Skye,

Data stores should be thought of primarily as temporary storage, or parameterization tables, not necessarily as permanent logging or large scale data use cases.   To create one, think of this as 2 steps, of which both will typically occur within the scenario creation operations.  To start simply select a datastore module and select Add, provide a name and then the most important step, Add or select a data structure.   It is the combination of the Data store and Data structure, that create the object.  If you forget a row in the data structure, you can simply go back to any Data store module and select Edit from the drop down and add rows.

One example I just setup was to capture a triggering event from a 3rd system, a Salesforce Opportunity Stage.  The reason I want to capture it, is that in some cases we have to hold processing the transaction > create a Workfront project until a secondary field is filled out.   So in effect, track the integration from Salesforce and leverage the datastore to 're-try' processing until all fields are properly managed in Salesforce.   This technique will use 3 scenarios

#1. A Watch Field triggered event to watch for a Salesforce Opportunity Stage to reach a certain stage.  This scenario will add every intake at this stage to the datastore where the key=OpportunityID, then a text column for status, and a date Changed field to timestamp the event.   Every new record has the status of 'Pending'.  In this scenario we submit to a subroutine scenario

#2 The subroutine scenario that uses a Fusion Webhook module as it's trigger.  This scenario actually processes the transaction and creates the WF Project.  When successful changes the status field to 'Processed' or perhaps a failure message

Then #3 a scheduled event that searches (iterates) on all records not 'Processed'. This scenario re-submits to scenario #2 which will either succeed due to the fields being managed finally in Salesforce, or leaves in a holding stage. 

The gotcha, make sure in scenario #3, you delete 'Processed' records older than 90 days old to prevent growth of the data store.   Remember you only have 100MB to play with so use your storage wisely. 

Hi @danielcl4 ,

We have developed a standard Design Document that we use to capture the following:

• Business Use Case
• Integration Overview
  • Expected Workflows (or Impacted Workflows)
  • Fusion Schedule
  • Dataflow
  • Data mapping (with highlevel object mapped as well as in connecting SFDC Account to Workfront Company)
  • Required Workfront Configuration
  • Out of Scope
• Data Stores
• Testing and Change Management
• System Technical Limitations
• Fusion Connectors & Keys
• Assumptions

In addition we export a copy of the blueprints.json (using the ... menu) and record a video of us walking through the scenario module by module.  Curious if others in the community use other things?  

HI Taufiq,

I would suggest that one of the best ways to manage Fusion and OneDrive is to switch your mindset a little, and have Fusion automatically create OneDrive folders in a dedicated drive space, for each project created, then create that folder in Workfront.  We suggest that you also leverage the native OneDrive product integration for documents as part of this.

Once that is performed, when the user uploads the document to Workfront, have them select this OneDrive (remote) folder.   Doing this will allow the Workfront Native connector to push that document into the OneDrive remote folder and it actually never exists physically in Workfront.  

Specifically to your point, having a remote folder in WF, for this document that was uploaded from OneDrive, it will not automatically be available in the WF object where the remote folder is created by Fusion.

We just built this very thing @alferaj16! Downloading CSV, checking for duplicate projects, gathering required project data, validating addtl info from Salesforce, creating project from template, making assignments, and creating a supplemental issue on the new project. 

Biggest headache was confirming/gathering all the required data to setup the project and fill in the custom forms. 

Happy to discuss if Andy and Ewan can't dig in deep!

Have you verified that the ID being returned from Fusion for the Original issue on the Project matches? I've had trouble in the past getting the original issue ID number and was using the wrong field.

This seems like it may be an issue with the Google Drive Module, sensing updated content.   Are you using a web-hook or watch folder, I believe the watch folder has to be triggered via a schedule and is often more robust.   

I often do not use GDrive and will instead look for new objects within Workfront, or S3 or other locations.  

Interested in learning more about this too @ewanh @andyhess 

This really depends based on your licensing type and model. I recommend reaching out to your Account Representative to inquire. Typically, what you are referring to as an automation would translate as a scenario. By connector you might think of these as an App and those may span scenarios, so as long as you aren't connecting to more than three applications across your different scenarios you SHOULD be okay in most situations.

For more information from our community check here.

To be certain...please check with your Account Rep!

@skyehansen ,

Yes, this can be a struggle.  Other than what is in our Experience League Documentation and the Community there isn't a separate one-pager.  Where possible I try to use Workfront modules and objects to get most of the Proof details.  For example proofs tie closely with Document Versions.  One of our Integration consultants says to get very familiar with the Document misc action createProofRest.  

Additional thoughts @andyhess or others?