Skip to main content

Ideas

Filter by idea status

10000+ Ideas

Selliers
SelliersLevel 4

Use of paragraph tag when pasting text into email fragmentsDeclined

We have discovered a strange ting that happens when we are pasting text into a fragment. If we are cleaning up the text in Notepad, and uses the text in a fragment we are running into some issues. It seems like if the text from Notepad has several paragraphs something strange happens. The first paragraph is recanalized as a paragraph and is placed inside a P-tag <p>.  But the other paragraphs that is pasted in is for some reason placed into div-tags <div> This causes problems with the design of the content. Explained in code this would look something like this:Notepad text:Here is our paragraph text oneHere is our paragraph text twoHere is our paragraph text treeIn our fragment in AJO the code for this would look like this: <p>Here is our paragraph text one</p><div></div><div>Here is our paragraph text two</div><div></div><div>Here is our paragraph text tree</div>As you can see the tree paragraphs are acting in different ways, one as a pragraph tag, the two others as div-tags. And it seems like there is used a div-tag to create line space between the paragraphs -where Notepad has space.This causes some problems with styling if you are using customized style classes since a p-tag and a div-tag isent the same thing - and in most cased has different classes. It would be great if pasting of plain text with several paragraphs could have the same tag conected to each of the parapraphs - like <P> is been used for all. 

Enable “Approve with Changes” to Route Proofs Back to Creator in Workfront ProofingNew

DescriptionWe are requesting an enhancement to Workfront’s Proofing tool to allow greater flexibility in review workflows. Specifically, we would like the option for proofs marked as “approve with changes” to be sent back to the proof creator for updates before progressing to the next review stage.Why is this feature important to youSome internal teams currently use other project management tools because they offer more adaptable review workflows. The inability to send proofs back to the creator for updates after an “approve with changes” decision in Workfront creates challenges for teams that need to revise content before further review. This feature is crucial for meeting compliance requirements and would facilitate broader adoption of Workfront across our organization.How would you like the feature to workWe would like a configurable setting within automated proofing workflows that, when enabled, routes proofs marked as “approve with changes” back to the proof creator. The creator would then have the opportunity to make the necessary updates before the proof continues to the next reviewer. This should be an optional workflow step that administrators can enable or disable based on team needs.Current BehaviorCurrently, when a reviewer selects “approve with changes”, the proof automatically moves forward to the next stage in the workflow. There is no built-in option to send the proof back to the creator for updates first. Our only workarounds are either manually uploading a new version and adjusting the workflow, or creating multiple automated workflows for different scenarios, both of which add complexity and risk errors.