I haven't had the sign-out issues (we haven't been migrated to the Admin Console yet), but I've definitely noticed the sluggish performance in attempting to access history.Even more bewildering, I experienced some phantom history entries last week within a scenario.  I have a scenario (still in the ...

Ah, thanks.  I didn't let the Watch Events module sufficiently process originally.

I'm working on a scenario with a Watch Events module--it's triggered when a custom project field (1) exists; and (2) is changed (the custom field is a date field).  I added a Set Variable module used to parse the date.  However, I've discovered that the custom field is not available in the mapping p...

That was my first thought, too.  But when I didn't see it listed among the custom fields, I found it in the API Explorer.  Apparently it's a native field; I just don't see it in the UI anywhere. 

I'm picking up work on a Fusion scenario that was started last year by a colleague in conjunction with a WF consultant (it was the last of our consulting hours, and work on it had not continued).  The scenario involves an integration between WF and Airtable, and I see that a unique identifier from A...

My scenario involved assigning multiple users to tasks, but the assignMultiple action requires that you enter values for both users and roles (or enter the emptyarray keyword if not applicable), so it should work for roles as well:

Hi Nick,I had to do something similar with tasks on existing projects, but I think you could do the same with template tasks.I downloaded and parsed the CSV file containing the tasks and assignment IDs, but instead of an Update Record module, I used a Misc Action module (with the assignMultiple acti...

Same.  Scenarios sometimes take longer to run (specifically, Watch Events don't always get triggered immediately), and the processing for even simple scenarios often takes longer than it should.

I can't find any info on action options either and had no luck playing around with the options string.You might need to simply attach the template and then update the predecessors to add the enforcement.This post helped me use a create a custom API call to update predecessors.  Originally I used it ...

Ah, figured it out.  In my original scenario I was parsing the newDatVal, which is listed as a Journal Entry object under the Watch Field module output.  If I explicitly tell the Watch Field module to output my custom date field and then parse THAT, I get the correct result.