If you try to edit the Planned Start Date or Planned End Date of a parent task, the date you enter gets overwritten by the dates of the sub-tasks. f the parent task dates must be a calculation of the sub-task date, then it shouldn't even allow you to attempt to enter dates at the parent level. Or, if it does allow you to enter them, it should give you an error message. The current way it works is confusing, because it lets you enter a date and then overwrites it. So if you just enter the date quickly without checking to see what it looks like after you save, you might be misled in believing your update was saved successfully.
I'm talking about a standard feature in MS Project which allows to collapse tasks at multiple Indent levels. It's called Outlining Tasks.It works something like this:When you select Outlining Level 1 - All the Tasks at Level 1 Indent will collapseWhen you select Outlining Level 2 - All the Tasks at Level 2 Indent will collapse and so on..If this is not clear please watch this video: https://www.youtube.com/watch?v=jzHNHW5Xrzs to learn more.
Problem:We are unable to identify employees by Job Role in a project plan or on the project Workload Balancer.The new functionality only shows 'Recent Assignees'. We are a very large organisation and we now have to create a report or user filter to find the 10 Project Managers in Denmark, go back to our project plan or project Workload Balancer and manually input the employee's name.Change Needed:The recent assignments logic is very useful, and an excellent idea for smaller organisations, however, for larger organisations, we also need the 10 project managers appearing in the search results.Please implement a hybrid list of Search Hits of Recent Assignments and Employees with the same Job Role.
It would be awesome to have a way to indicate if due dates are firm and has to happen on that date or if it is ok to complete as soon as it becomes available (but no later than due date) - tasks especially it would be helpful!
When there is a long running project, documents start to be archived and it can lead to the project being delayed. If the document archiving could wait until the project is complete, that would be ideal.
Hey Adobe, it would be great if you coul change the language simply in the controls of each program. Further it would be great if the effect search bar would respond to the effect names in other languages.e.g. - I use premiere pro in German - but I watch tutorials in English. If I want to replicate the tutorials its a pain to find out the translations of the effects. I'm sure you can fix that quiet easily and it would be a relief for a lot of people.Thank you very much for your consideration. Kind regardsJulian
Request for Feature Enhancement (RFE) Summary: Better UI experience for Settings and Rules section in the metadata schema Use-case: To be able to create metadata schemas easier and faster Current/Experienced Behavior: 1. When scrolling to the bottom of the metadata schema form (especially when it has numerous fields), the "Settings" and "Rules" section are no longer visible. 2. When selecting fields already in the metadata schema, "Build Form" option is also visible. This can lead confusion to the users as users might think that "Build Form" is a setting of the selected field. Improved/Expected Behavior: 1. When scrolling to the bottom of the metadata schema form (especially when it has a lot of fields), the "Settings" and "Rules" sections should follow with the scrolling or "stick" to the page. The "Settings" and "Rules" sections should always be visible so that it would be easy to change the settings when selecting the fields. 2. When selecting fields already in the metadata schema, "Build Form" option should not be visible so that "Settings" and "Rules" section are the only ones displayed. Another option is that the "Build Form" can also be placed in the left side of the page so that it would be separate from the field settings. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
We would like to see the ability to create billing records with $0 amounts / actual revenue for any R&D projects we complete.At the moment, it let's you override by using company billing rates, however, since user billing rates still apply when adding hours to billing records, this defeats the purpose, as it just takes the user billing rates anyways (even with a company billing rate override).
I would like to request that users have the option to select up to 18 months in the Workload Balancer. Currently the longest a user can go is 3 months, which doesn't give user enough insite into their workpipeline.
Build in a tab into WF that stated the average time for similar tasks and then asked the team member to confirm if that allocated time was accurate. We could possibly just have 2 radio buttons, one that indicated that the recommended time was accurate and one that allowed you to select "other" and input the actual time allocated.
When making an update on a project, it would be nice to have a box to check to "Notify Project Team", who would then all be cc'd on the update. By "Project Team", I mean all Personnel on a given project. This way you won't have to remember who all to tag. ALL who are on the "Project Team" would get the notification.
My company develops some very detailed PPT presentations to include in-depth speaker notes. We currently have to create PDFs in notes view of our PPT presentations in order to view and comment on the notes section. We would love to be able to proof those notes directly and avoid the extra steps.
Managers should not have to depend on Project Creators to "share" correctly. If they are left off of the project sharing, they do not have visibility to their direct reports task assignments (unless you do wonky workarounds like creating a report run with the access level of system administrator).Currently in Setup > Access Levels > you can set up rules for projects to automatically grant view access to the project creator's manager.Likewise for Task Access Levels, you should be able to set up a rule to automatically grant view access to the task assignee's manager.
When performing more advanced customizations of forms, it's not uncommon to deploy complex CSS to present Marketo's form styling differently. As an example, this screenshot shows a Marketo form field with three radio buttons with transformation: In order to maximize accessibility, only the text ( e.g., "PDF - Option for U.S. [...]") is stored as the display value for Marketo; the rest of the styling, including the unique imagery for each radio option, is performed via CSS. Therefore, I need to target the label elements for each option. By default, Marketo outputs a randomized ID to each radio and label, such as mktoRadio_39390_0. This does not relate back to the field name itself, though that is set is the input's name attribute. However, if a form is updated—even if the update does not touch any form fields, like with an HTML text area change—the randomized ID changes every time. This leaves the form designer with two options: Write supplemental JavaScript to assign a unique-but-consistent attribute to the radio buttons' labels Update CSS selectors every time a form is updated Neither of these are ideal. Because the field name is already being pulled for the name attribute, could the code output be updated to set IDs based on the field's API name? For example, if the input has name="billing_format", could the radio buttons' labels be named like "billing_format_0", "billing_format_1", etc.? This would provide a consistent selector for styling.
Reference - Case Number 00297963https://amazonaccounting.my.workfront.com/report/61bbc0e1004a4c432da4912d216478a0/detailThe above issue report is group by Project Name and provides a total of a custom field called "Total Annual Support" which is a custom calculated field. I would like to sort the report so that the project with the highest Total Annual Support value is at the top of the report.Currently, the only possible way I see is to run the report and manually click on the header name for "Total Annual Support" but the system sorts based on each individual issue value and not the total at the project grouping.It would be great if there was a switch to indicate whether to sort on the individual issue value or the group total value.Thanks,James
‚Hi, we need an hours/user report which shows General Time, the breakdown of hours against those items and the notes so that we can see how much time is lost on non-chargeable items and on what. Have spoken with your helpdesk and this isn't currently possible. I have to do this manually by logging into each user and reviewing their timesheet then manually add to a ppt template. Thx
A trigger event that occurs for the winning lead of the merge An example of where this is useful is that when 2 leads become merged there could be new webpage visits/anonymous activity on the winning lead activity record after the merge which means that we should recheck attribution campaigns to see if this person's first touch parameters should be updated I am sure there are more use cases for a trigger like this
We are getting daily notifications with "Marketo is unable to update the following records in Microsoft Dynamics." These are records that have recently been merged and are no longer active (deleted) in Marketo and Dynamics due to that reason. We receive this notification because updates must be in process. You can ignore these notifications as they do not cause sync issues. We would prefer that these notifications do not come in at all since the records no longer exist in both systems. Hence, no actions are needed in Marketo or CRM.
We want to give users permission to be able to import leads but we ONLY want these users to be able to import leads using “Skip new people and updates” List Import Mode ONLY. i.e. we don't want to give them permission to import leads using “Default” List Import Mode as we don't want them to be able to import new leads. Would be awesome if user Role permissions could be configured to do this
I'd like to have the ability to display a field based on what role, team, group a user is in.
We're managing a large implementation across several countries where we have limited contact with the users. We're not sure what our users are finding helpful (and equally importantly, what they're not using at all). It would be good if administrators could see which reports are being viewed. Not just total figures but the ability to see which users are accessing which reports would be useful as well, as we would contact the users of deprecated reports or such.
There are teams that are interested in seeing if there could be functionality to see when an approver has downloaded a document. This is important as it will allow document owners to see if the approvers/team members are taking action on the document.
Hi,In order to manage properly all risks in a project, it would be great to have custom forms/fields to have more information in risks menu.The vision is to combine the default fields with new one's, in a custom form, as occurs in issues and tasks. Is this possible?Also would be great to have the possibility to convert risks into other objects(tasks or issues)
Request for Feature Enhancement (RFE) Summary: "Build Form" should "stick" on the metadata schema editor page Use-case: To be able to create metadata schemas easier Current/Experienced Behavior: When we are creating metadata schemas that have a lot of fields, it is cumbersome to drag the field from the top of the page (since the "Build Form" scrolls with the page) and drag it again to the bottom of the page Improved/Expected Behavior: The "Build Form" should stick to the page and not scroll with the page so that it is within easy reach. The "Build Form" interface then should have a separate "scroll" from the page, to scroll through the field types. We also think it would be better to have it in the left side of the screen and collapsible so that it does not intrude as much in building the metadata schema. Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Request for Feature Enhancement (RFE) Summary: Default option values when creating dropdown options in the metadata schema editor Use-case: To be able to create metadata schemas faster especially when creating dropdowns with a lot of options Current/Experienced Behavior: When creating dropdown options, we need to enter manually both "Option text" and "Option value" Improved/Expected Behavior: When creating dropdown options, as a default for the "Option value", it should have the same value as the value inputted in "Option text" Environment Details (AEM version/service pack, any other specifics if applicable): Customer-name/Organization name: Screenshot (if applicable): Code package (if applicable):
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
