Hi @Shawn Flege‚ The main approach I have seen is to use issues to represent RAID items on a project. Each item type would have a queue topic and a related custom form (if needed). Routing rules can be applied as needed to automatically assign the item to a person or a team. I have also setup a sta...

Thanks, Darrin. That documentaion is looking great excisted to see it when it's ready to go. I would also add that it would help if there was a section that gave general instruction regarding the way GET, POST, PUT and DELETE calls should be structured independent of a specific object. dc

Darin,‚Is this usage of the message body documented? I feel like the documentation I have seen says to use the query parameters to supply field inputs for a put.‚ThanksDaniel‚ @Darin Patterson - inactive‚

Thanks, Sam. It would be nice if there was an announcement when new connectors are released.

Is that the output of the map card? If so, you look at just returning the value you want instead of the whole object to the new list. Daniel Cooley Rego Consulting

You would use a return card to return a value to the parent flo. Daniel Daniel Cooley Rego Consulting

I'd take look at this article if you haven't seen it already. https://experience.workfront.com/s/article/API-Basics-638808549 Daniel Cooley Rego Consulting

I think Jim is on the right track. You will need a for each loop to process the list. In the child FLO set the input field type as an object. In the event card on the child FLO set a key equal to userID. Pass that userID field to a return card. You will also need to add that userID to a new object t...

You cannot move hours on their own. You'd have to move the attached object. If they are logged to the project there won't be anything you can do. What's the use case here? Maybe there is another solution? Daniel Daniel Cooley Rego Consulting daniel.cooley@regoconsulting.com