How to Make Collaboration Flow in Akeneo PIM
Akeneo PIM has workflow capabilities for product information that enable you and your team to collaborate on work with the usability Akeneo is renowned for, with none of the inflexible rigidity other solutions may present.
Teamwork Assistant
One reason you might need a “workflow” is to ensure that your team stays on schedule and required work doesn’t get left behind. For example, you have a major launch of a new line of products coming up, and everything must be ready in time for your different channel and marketing teams to promote and sell them on the same day. That means everyone collaborating on those products needs to track progress on enrichment tasks that have been assigned to them, and be notified when there are new tasks for them to take care of. That’s where Teamwork Assistant comes in. Each set of products that needs to be worked on is grouped into a Project, based on their category, channel, and locale. For that Project, a due date is set, and those who have edit permissions for the products selected in the Project will be notified when required attributes need to be completed, based on the attribute groups they have edit permissions on. For example, Mary on the marketing team is responsible for ensuring product descriptions are complete, well-written, and aligned to the brand voice. So she has edit permissions on the Marketing attribute group. If a required Description field for a set of products in the Project isn’t completed, she will be notified repeatedly before the Project’s due date to do so. If everything is good to go with the required attributes that she has edit permissions for, then she won’t be bothered, and will only be notified when everything in the Project is complete. As you would expect, everyone involved can see the overall progress of the Project. And to help everyone be productive and focused, they can even see just the products in the Project they need to work on the Product Grid, just like a View.
Proposals and Approvals
We often see bad product experiences everywhere. “Product description to come when Peter gets back to me with the details” is not something anyone wants to see when researching a product. This is another reason you might need a “workflow”: when collaborating as a team on the product record, you must ensure information doesn’t get out into the wild that hasn’t been checked and approved by a manager first. Akeneo PIM to the rescue here! Akeneo PIM Enterprise Edition provides granular and flexible permissions settings according to your business needs. I won’t go into detail on all of them here, but some that matter for proposal submissions and approving them are the permissions that can be set for a category in your product catalog. These permit user groups to either own products within the category, edit them, view them, or have no permissions at all. Someone who can edit a product in a category, but does not own the category it’s in, will be able to edit a draft of the product information and then “Send for Approval” – individually, sequentially, or as part of a Bulk Action. The product(s) status will change accordingly, and the users that are part of the group that owns the category will be notified that they have proposals sent for their approval. They can view those in a single place from the Proposals menu under Activities, for a specific product in the Product Edit Form, or by creating a custom View that includes the Draft Status filter. Whatever suits your style of working the best! Whether the manager approves or rejects the proposal(s), the product(s) status will change accordingly: “Working Copy” ready to be published, “Waiting for Approval” or if the proposal doesn’t pass muster, back to “In Progress” it goes.
Shopify
Adobe
Salesforce
SAP



















