Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Rich Text Editing Options for Tasks Details > Overview > DescriptionNew

Description - Enable Rich Text Editing for Task Details > Overview > Description.Why is this feature important to you - It would give us more tools to emphasize and communicate key details in the instructions and provide better readability for the user assigned to the task. Better readability means faster turnaround and fewer mistakes.How would you like the feature to work - Give us the same formatting options that are here in Ideas, i.e., preformatted styles, text color, text size, font, insert/edit code, insert video, create table, alignment, indent/outdent. Current Behaviour - Only plain text can be used, so instructions for tasks that are more complex are created in Word and uploaded, then a note is added to the task to see the attached Document for instructions which is less efficient for everyone.__________________________________________________________________________________________________ Here's a lot more UX friendly example (overly styled/colored for emphasis): Description - Enable Rich Text Editing for Task Details > Overview > Description.Why is this feature important to you - It would give us more tools to emphasize and communicate key details in the instructions and provide better readability for the user assigned to the task. Better readability means faster turnaround and fewer mistakes.How would you like the feature to work - Give us the same formatting options that are here in Ideas, i.e., preformatted styles, text color, text size, font, clear formatting, insert/edit code, insert video, create table, alignment, indent/outdent. Current Behaviour - Only plain text can be used, so instructions for tasks that are more complex are created in Word and uploaded, then a note is added to the task see the attached Document for instructions which is less efficient for everyone. Thank you for considering!   

Selliers
SelliersLevel 4

Update email master templates in an always on JourneyInvestigating

We have found an issue in AJO making us concerned about how to handle emails in an always on activity - when the master email template is been updated. It seems like there is now obvious way of changing and updating a template, and at the same time keep the content that is created in a template used in an running Journey. Changing the master template directly in prod, or from a upgrade package is no problem. The issue is how to keep the created and customized content used in that template you are updating. In many cases you are just updating the "framework" like header/footer or other more than less static content in a template. And in a Journey you create the relevant content for this activity using the "static" framework. But when you need to change/upgrade the framework, and change the template in use with the new and updated version, the customized content is been deleted. Is is not able to update just the template, and keep the customized content inside the template. We strongly suggest that there could be a feature making it possible to update an email "master template" that is in use, and at the same time be able to keep the customized content that has been created using this template. The template is still a template and that framework is used in several Journey's. We run into serious problems it we need to re-create all content just because the the template has an update in the static frame content. If you in the back end could split between what is template code and content code this might not be a problem. It seems like those two things is merged together and AJO cant see the difference between template code and customized content code. 

DjTFoxLevel 2

Bulk Delete Feature for Journey OverviewInvestigating

OverviewThis change request proposes adding functionality to allow users to delete multiple journeys simultaneously from the Journey overview, with built-in dependency checks to prevent deletion of journeys in active states.Current BehaviorCurrently, users can select multiple journeys in the Journey overview (indicated by a blue line showing the number of selected items), but must delete journeys individually through each journey's ellipsis menu.Proposed ChangesEnable bulk deletion of multiple selected journeys through a single actionImplement/Keep as is - dependency checks to prevent deletion of "Published" (including "In review", "Dry Run") journeys. Only delete when status is Draft, Draft (Test), Finished or similar. Add a "Delete Selected" button that appears in the blue selection bar when multiple journeys are selectedDisplay a confirmation dialog showing:Number of journeys that will be deletedNumber of journeys that cannot be deleted (with their states)Option to proceed with deleting eligible journeys onlyValidationOnly journeys in Draft, Draft (Test), Finished or similar status can be deletedIf mixed selection (some eligible, some ineligible), provide clear feedback on which can be deletedAfter deletion, the selection counter should accurately reflect remaining selected itemsError HandlingIf deletion fails for any journey, show appropriate error messageProvide detailed feedback on which journeys were successfully deleted and which weren'tBenefitsImproved user efficiency when managing multiple journeysReduced risk of accidentally deleting active journeysConsistent user experience for bulk operations

Selliers
SelliersLevel 4

Moving landingpages between SandboxesInvestigating

Today: Landingpages are used for opt out (unsubscribe) to emails. Link to this page is placed in a email fragment in the footer of all email. A standard way of doing this. When this link to this page is created in the email designer tool, it adds a landing-page-id to the link. This in a unique ID that need to be there present for the link to work. And here comes the challenge .... If you use a Sandbox for testing, that many do. We have all our email fragments present in the test Sandbox. And it you then have created links to a landingpage for opt out, that page does not exist in the test Sandbox, or the other way around.The problem:We are running into a problem either way we look at this. If we create the link to the opt out page from the test Sandbox, this will not work when moving the fragments to a Prod Sandbox. Or if the link is created in Prod it will not work in Test. The result of not having the right landingpage present in eighter Test or Prod we are not able to send Proofs. The need:It is not a sustainable solution that we need to change the landingpage-id in this out out links to get email fragments and Proof sendings to work, when working with a test and prod environment. Especially when you easily can move fragments and templates with no problems between Sandboxes. But in most cases it is a link in a footer fragment that will not work if you aren't able to move the landingpages as well.