What is it?
Besides the option to run campaigns where each campaign more or less follows a different process, it is also possible to configure one general idea process and open different thematic campaigns on top of such a standard process.
This requires the definition of the idea workflow and a parent-child relation between a 'campaign parent' and the 'idea children'. In the following, the process of creating the campaign page and the parent-child configuration is described.
The Parent-Child feature enables you to automate the connection creation and grouping of content elements.
How does it work?
Creating a campaign entity and a first campaign example
To start with, you need to first create an entity that will reflect the template for any thematic campaign that you want to run in the future. You need to navigate to the Settings Wheel > Entity Configuration > Entity Configuration. Here, you can add a new template/entity, for instance, with the entity title: campaign. Add all the fields that you want to provide as part of the template. Apply the right permissions to define which user role is allowed to view and create in general a campaign.
You can also make use of the visibility tab to allow for more specific content-related campaign access. Please talk to your Customer Innovation Success Manager to enable this feature.
Once done, all allowed user roles will be able to create a campaign from the 'create' button in the main navigation menu. They can thus fill out the campaign template that you have defined.
You can further make use of the standard or a custom landing page to place each campaign prominently.
Allow the submission of ideas
The more critical part is now to allow the submission of ideas to such campaigns. Technically speaking, a parent-child relationship is created. Via a submission button, each new idea will be added as a child element to the parent campaign automatically.
On specific campaigns, users will find a Submit action button on the right-hand side of the detail page of the campaign, i.e., the parent element. This means that by creating the child element via the action button, the relation to the parent element is set automatically. Once clicked, the submission form for the idea intake will open, and the idea submitter is asked to fill it out. This step of the process is defined within the idea workflow configuration.
To make this submit button visible, you first need to enable the parent-child feature on the parent element, e.g., the campaign entity. If activated by your Customer Innovation Success Manager, you first need to enable the parent-child feature in the entity configuration of the parent element via the Settings Wheel > Entity Configuration > Entity Configuration and by clicking on the pen icon of the parent entity.
Here, you can select which entity (from the list of available entities) should become the child element. That means that you should have already configured a second entity, for instance, called 'idea'. If this exists, you will be able to choose this entity from the list of child entities.
You also have the option to activate a specific Kanban Board per campaign which will hold all submitted ideas to the respective challenge.
Once saved, a new configuration tab will appear called 'parent-child configuration', and a new static field 'Allow Submissions' is added to the Field Configuration of the respective parent entity.
On the parent-child configuration tab, you can now choose to hide the respective child element from the Create menu. This checkbox is unchecked per default. If the checkbox is checked then the child entity type is not shown anymore as an option via the Create menu to the users who have permission to create elements. However, note that child elements may still be created via the Submit button on the detail page of a parent element.
Also, via the parent-child configuration tab, you can now check the box to inherit the visibility of the parent to the children. This means that only participants invited to a specific campaign will be allowed to view the related submissions.
As a second condition, the visibility tab needs to be activated for the parent (e.g., campaign) and the child entity (e.g., idea). The Visibility tab is displayed when you create or edit an element and needs to be activated by your Customer Innovation Success Manager.
You can choose from two different options to grant visibility access.
- Choose to invite all users if you want to give all users access to the element with the respective system permissions. This is checked by default.
- Note: If a user has no permission to see the entity type, they will not see this element. If you check the box Send notification to the invited users, a warning message will appear to prevent you from mistakenly sending out notifications to a large number of users when creating a campaign element.
- Choose Others if you want to restrict the visibility of this element further. Now, no user can view the element except for the ones that are added via the search field below. You can add single users and user groups, roles, and contexts (often: Business Units).
Typically, you would choose others in the visibility tab and add the respective roles, users, or user groups.
Note: When the Parent-Child feature is activated for an entity, a new static field Allow Submissions is added to the Field Configuration of the respective parent entity. The status of this static field controls whether a user is able to create child elements or not. If the Allow Submissions button is set to Active, the Submit Child button is available on the parent element, otherwise if the status is set to Inactive the Submit Child button will be disabled on the parent element. Also, if the Allow Submissions field is set to Inactive, no parent element can be added to a child element via the Relations tab. This can be set from the create/edit form of the specific content element. Please do not forget to add it to the create/edit form configuration.
Once the visibility of the parent is set and the parent-child feature is configured, new children content elements can be added from the respective parent content element by clicking the corresponding button, i.e., "Submit [entity]". Now, the visibility restrictions put on the parent element will be inherited by the child elements.
Finding all idea submissions of a campaign
If activated, you also have the option to display all ideas in a Kanban Board and along different swimlanes within the specific campaign page. After the activation of the Kanban Board on the tile for activating the parent-child feature, a new tab Kanban Configuration is added (1). Here, you select any list field from the swimlane field (2). This field can be any single select list field from your child elements. Don’t forget to click the Save button once you are done (3).
On the Board tab (here Idea Board of a specific campaign), you find the activated Kanban Board with the different swimlanes. Each swimlane has a title (here: Sustainability, Artificial Intelligence, Revenue). There is also a numeric indication of how many child elements belong to this attribute (and based on your applied filter sequence).
You can drag and drop the child elements to update them according to your needs.
You can also use the child tab on the detail page of the parent element (2). This tab will only list all submissions to this campaign.
There is a Filter (1) section that allows you to narrow down the list of child elements in different ways:
- By applying a Search.
- By applying different Filters. The shown filters are:
- General filters, e.g. Followed by
- Child element filters e.g. all dropdown filters, or user search field filters
- By applying a rating filter (if there are ratings configured for your child elements).
Combining the campaign analysis with other ITONICS modules
Since the created parent and child entities are regular entities defined in the entity configuration, it is possible to use any ITONICS module, i.e., radar, matrix, board, network graph, Explorer, tag cloud, custom dashboard for further analysis. It is thus also possible to compare submissions between different campaigns or re-allocate one/multiple submission(s) from one campaign to another campaign.
To activate any module, first navigate to the entity, e.g., idea, for which you want to define a visualization, i.e., via the Settings Wheel > Entity Configuration > Entity Configuration. Click on the edit icon of the respective entity and activate the respective module on the page you landed.
After defining attributes (plus marking them as rating criteria) and defining rating criteria, you will be able to define a default view for the Matrix, Radar, and Board. Once the module has been activated, you will find a new tab for the default module configuration.
This will help you to oversee your complete idea portfolio. Furthermore, you can use the filter options, such as the "relate to" filter to narrow down your view to a specific campaign by entering the campaign's name into the 'relate to'-search bar.