Adobe Employee

🎬 [VIDEO] Top 3 Reasons to use Companies

Forum|Forum|1 year ago
May 2, 2024
2 replies
2586 views

We’ve got another Top 3 video with your “On-Demand Workfront CSM”! This time we’re talking about a commonly overlooked (but helpful) object in Workfront – Companies!

Check out the video below.

Looking at adding Companies into your mix? Here are some tips!

First things first – documentation and tutorials!
Test in the Sandbox first! See what your vision can look like without impacting your live, production environment.
- The Adobe Workfront Preview Sandbox Environment
Build a Report or a View that lists the impacted objects you want to move. If it’s Users, then a User View/Report. If it’s Projects, then a Project View/Report. If possible, use Groupings to make it easier to organize the work.
- Create a basic view
Bulk edit or inline edit to assign your new companies.
- Edit Projects in bulk
- Edit user profiles in bulk
Don’t delete anything – just add and test, add and test, until you’re sure that everything works with the new companies. Then, don’t delete – just deactivate.
- Deactivate or reactivate a company

Interested in new ideas and approaches? Register for our upcoming workshops our Experience League Events page. We hope to see you soon!

Workfront

RandyRoberts

Community Advisor

I use companies as clients. I have a different company set up for each product/initiative/MSA-contract, so for us it goes by product or initiative. I attach a form to each "Company" with information about that product/initiative/contract. When a project is opened, the user chooses the product/contract code. Since we are in the pharma/health industry; from that company entry I can prepopulate a lot of the information we need for the project. Example:

Company name is "Humira", from that I know the manufacturer is Abbvie, the therapeutic area is Arthritis/Crohn's/psoriasis, the billing cycle is 60 days, the buyer is Med Affairs, the contact is Jane Doe, the product is pharmaceutical, the product life cycle is post-launch, etc. All this is in calculated fields on the project form that pull from the company form.

This allows the user to not think about filling out a form and concentrate on getting the job done. Plus, it eliminates all the wrong choices you might see in a user-filled form.

V

VynetaRy

Level 2

@randyroberts This sounds like the perfect solution to a new Team that I am setting up to manage partner company relationships. I am fairly new to Workfront and having a little trouble wrapping my head around the calculated field part of this. Can you explain the calculations you would have in those fields to pull in the information? I love the idea of prepopulating fields so our customer reps don't have to enter information that already exists.

@cynthiaboon thank you so much for the video and discussion. I had been brainstorming a way to handle this and your post made it all click.

V

VynetaRy

Level 2

I should also add that using a calc field can "bridge the gap" when you want to report on something that's too many hops away.

If I want to know a project owner's manager's name on a document report; that's too many hops. But If I put a calc field on the document's project that lists the owner's manager's name, I can read it from there on the document report.

I just made that up off the top of my head but hopefully you get the gist. Maybe someone can give a better example of the same concept.

@randyroberts Is there a way to reference information in more than one company? For example, if I have a project that is assigned to one company, but there is a different company that also has pertinent information, is there a way to use a value stored in a custom field form to reference an associated company?

I can get {company}.{DE:InfoField} to work, but I can't seem to get {DE:ParentCompany:name}.{DE:InfoField} to work. For reference, ParentCompany is a Company typeahead field.

TaraMc2

Level 2

I'm trying to understand if companies are the right approach for an upcoming initiative. Right now, we only use one company and all users reside and work within that company even though they may have uniquely different work. However, we are moving toward allowing our external clients to access the Workfront tool. We want them to be able to enter a request type that currently sits in our global company to begin the review of assets for marketing purposes. We don't want them to be able to see any other information outside of their own work. We have over 200 clients. Would companies make sense in this instance? Should we only have one universal company for all of the clients or should we have 200+ companies?

RandyRoberts

Community Advisor

Putting them in separate companies is a lot more work but it affords you flexibility. All in one Company is easy but rigid and non-flexible. If you ever want to treat one company different than another, like with permissions, layouts, sharing options, etc., you want separate companies

CynthiaBoon

Author

Adobe Employee

Randy, as always, you said it way better (and more succinct) than me! 🤠

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded