TaskRay

Salesforce doesn’t have a ready-made Flow template that automatically creates a parent and multiple sub-projects in one go, but you can get it working with a little layering. 

Here’s what I usually do: start with a Record-Triggered Flow on Project creation. Once the parent project is created, use a Create Records element inside the flow to generate the sub-projects. You can define them as a collection if you have a set number, or even loop through a custom object/list if it’s dynamic. Don’t forget to set the Parent Project lookup field on each sub-project so the hierarchy sticks. 

If your sub-project structure is always the same, you can store a template list of sub-project types in a custom object and loop through it in the flow. That way, whenever a parent project is created, the flow spins up the sub-projects automatically with the correct hierarchy.

Hi @Tumiloju A-Olugbamila, 

Ashwini is correct that you can certainly automate Project creation from an Account action rather than an Opportunity. In the article previously shared, stick with the sections labeled "Simple Repeatable Process" as a guideline. It sounds as though you will have two options for Templates that depend on whether the TaskRay Project will be for existing or new clients, so you may need to include a decision element in the Flow that you create and select the applicable Template based on that. If you'd rather not create a Record Triggered Flow, there are also certainly options to create a Screen Flow to tailor more direct steps for creating a new TaskRay Project. 

If you'd like more specific help you can 

Submit a Ticket as well. We're happy to help!

Hi Nikhilesh,

The short answer is that yes, you can delete TaskRay Roles that have been created. The longer answer is that it will help to understand why you want to delete this Role as well as where the Role has been utilized up until now. Is the Role simply no longer going to be used going forward? In addition to that, there are further considerations for the relationships of any TaskRay Role. Prior to deleting the Role, it should also be removed from any current TaskRay Project Team, as well as reassigning any TaskRay Task record that the Role been assigned as Owner. If you delete the Role, there is also a corresponding Queue with the same Name that also should be deleted. 

We're also happy to have a longer conversation with you specifically so we can better understand your whole Use Case. I would recommend reaching out to your Customer Success Manager with TaskRay for a meeting where we could talk through the specifics and be sure we've addressed all concerns.

Thanks!

Hi LaToya,

Thanks for that additional context! I believe we can use the Repeater Screen Flow Component along with the packaged Bulk Clone TaskRay Projects Apex Action to help us get everything created the way you need it. I opened a Support Ticket for this so we could take a deeper dive into resolving this with our full resources. I expect that you got a notification from me a short time ago that includes a recording of an example solution.

Talk to you soon!

Ben

Hi Emily,

That Use Case is absolutely something that we support by assigning the TaskRay - Standard Access Permission Set to the necessary User without also assigning a TaskRay License. They will be granted access to our "behind the scenes" actions and be able to trigger your automations that include Project creation logic.

You're good to go!

Hi Kim,

Thanks for reaching out about this. I did some testing to confirm the expected behavior in my Org, and what I found was with OWD set to Private for TaskRay Project, TaskRay Tasks, and the Project configured as Private, that as long as a User is on the Project Team they will have visibility into all of the Tasks, and therefore all of the Time Entries, on the Project. With that said, I was able to create a Restriction Rule to test being able to hide TaskRay Time Records to only see Records Owned by a the Running User for Users of a specific Role: https://share.taskray.com/bLuvrq0r

Restrictions Rules may be a good way to remove access to TaskRay Time entries even with our Sharing of TaskRay Records in place.