With a second rule we can react in two situations. Rule Two: Adding to a manager’s past clients list when a manager is changed or removed To do this, add a second event: After saving a new profile. You can also clone this rule and change the event for greater power. Otherwise profiles would have to be saved twice in this situation. You can also have this rule react to profiles being created if the manager may be delegated when data is first entered into the profile. These may require the addition of a condition that makes the rule only fire if the client did not have a manager before (use a data comparison) – as currently the rule fires every time a profile is updated – but this does not cause any issues if “enforce uniqueness” is checked. You could choose to add other actions, such as to display a message on the site such as “Assigned manager is ” or send an e-mail. Check the box “enforce uniqueness” and select “prepend to the list” if you wish to have newest clients at the top.Item to be added: profile2:user (the user of the client profile being updated).List to be added to: manager:profile-manager:field-clients.We use the ‘entity fetched’ variable provided by the previous step to achieve this: Add an action “Add an item to a list” – this is needed rather than ‘set value’ as the clients field can hold multiple values.note that this is actually accessing data through the entity reference field to get the new manager’s UID – pretty cool!.Data selector= profile2:user:profile-client:field-current-manager:uid.The type of this entity is User – the user who is being assigned as the client’s manager. We need to load the entity that will be altered by the other actions. To have access to the relevant fields later on and to be sure the rule only fires if the field is not empty: Event and conditionsĮvent: After updating an existing profile You will need the Rules and token modules installed and enabled The basic rule: Add client to the manager’s ‘clients’ entity reference field when a manager is assigned to a client. We are also going to set up a second rule that fires only when a currently assigned manager is removed or changed, and to make things more fun we have a “past clients” reference field for the managers which former clients should be prepended to.
DRUPAL RULES ADD FIELD TO ENTITY UPDATE
When a manager is assigned to a client, using the manager field on the client’s profile, the objective is to update the “clients” field on the manager’s profile to match.
The client has a user reference field called “manager”, which can only contain one item, and the manager has a user reference field called “clients” which may contain multiple values. In this example, the user entity can have an attached customer profile or a manager profile, containing different fields, using the profile2 module. Creating a synced client / manager relationship in rules There is a module to migrate from references to this module should referencing other entity types become a requirement.īoth modules work with rules in the same way, but if you wish to work with more than just user, node and taxonomy term entities you will need entity_reference.
The module is a little more complicated to set up and use, particularly for anyone previously unfamiliar with reference fields. It is possible to create references to any entity type, including custom entities. Entity referenceĮntity reference is a powerful module which is not restricted to any predefined entities like the References module. References is a simple module which emulates the node and user reference fields from Drupal 6. There are two modules commonly used to enable entity references in Drupal 7: References These field types allow the definition of relationships between two things (e.g. It’s now possible to create new entity types and many Drupal 7 modules take advantage of this to provide enhanced functionality and performance – for example, the Commerce module with its line item entity type and profile2 module’s profile types.Įntity references replace the role of the user and node reference fields from CCK. In Drupal 7, nodes, comments and users are all examples of entities, configured from the same base entity system. With entities, there is no longer anything special about nodes. Content types have to be types of node by definition, and come with comments, revisions etc that may not be relevant in many use cases and cause an overhead. D6 used a system of nodes, expanded by the CCK module to provide configurable content types. To understand this concept, it’s necessary to look back to how things were in Drupal 6. Drupal 7 is built around entities and entity bundles.
0 kommentar(er)
