Build better products with our product team
There isn't any way currently to restrict the rejection of logged hours for a closed timesheet. Project owners should not be allowed to reject time after all timesheets are closed.
Hi, If we use a generic email or an alias for a scheduled report, if a user unsubscribes, all the recipients do not receive the report anymore.Can we change that ? Regards,
We do not want our users to have administrative access to timesheets and hours, as that would expose the timesheets of everyone in our instance to effectively all our users. And it would be incredibly helpful for people, Plan and Worker licenses alike, to be able to log hours directly on the Hours tab of the project. Our projects don't always have tasks created for them to log time against. And we are only requiring people to log time at the project level.
It would be really helpful to be able to log task time from either a report or from the project screen. We need an easier way for workers to bulk log their time on a project basis.It is unrealistic in our case to expect users to log every minute on every task they complete one at a time by either using the home screen clicking one by one or going into each task one by one from the project level.
Tie the percentage complete on tasks to the time logged on the task. For example, if the planned hours on a task is 5 hours, and the assignee logs 2.5 hours of time, the percentage complete should automatically adjust to 50% complete rather than the person having to manually adjust it. If there are 2 people on a task and one person marks their task as "Done with my part" and the other person hasn't logged any time, the task should automatically adjust to 50% since on of the two people have completed the task. This should at least be an option on the Setup page where you can turn this functionality on or off. It seems to already be in place for the project percent complete but it would be nice to have this functionality for the task level as well.
The Post title says it all. We have a lot of Review Licenses in my Company (approximately 32% of users); they do a lot of "review" work in Workfront and right now, they have no way of recording time spent on a Task or Project. I recommend adding the ability to log time to a Task/Project to the next release, if not sooner! Regards, Jay Schertzer Intranet System Administrator Guild Mortgage
No text available
The new experience platform debugger is much worse than the old experience cloud debugger for Analytics debugging. It needs to be much-improved before it will be useful.1. The top half of the output is all information that is not useful for day-to-day debugging/testing. The key information, like Page Name, Link Name, Events, eVars and Props are all below the fold, requiring the user to scroll to see anything useful.2. Unless you scroll all the way to the bottom and use the bottom scroll bar, it is not possible to scroll right/left in order to track the changing data (it doesn't always automatically scroll along, and in any case sometimes several hits are fired in quick succession so you need to scroll left to see the first ones). 3. Clicking on an empty cell opens the details/copy dialog box, which is pointless. In the old 'cloud' debugger, clicking an empty cell just engaged the window so you could then scroll left/right with the keyboard arrows easily, meaning you could keep the variables you were interested in in the viewport more easily. Suggested improvements:1. Allow users to FILTER for the variables of interest. There should be an option to 'remember' the filter so that it isn't necessary to laboriously filter out all the top and bottom half of the data every time you use the debugger.2. Clicking on an empty cell should not open the details dialog. Instead it should engage the window so the user can easily scroll left/right using the keyboard arrows.Alternatively, allow users to MOVE the rows of interest up/down. This would allow us to move the required variable rows to the bottom so we could scroll using the scroll bar without the data being out-of-sight above the fold.
It would be very helpful to be able to track lead source information via UTM parameters in a more simplified way. Currently, you either need to: - create a form with hidden fields for the UTM parameters to pass onto Marketo - write Javascript on the landing page The limitation of creating a form is that in the case of a highly targeted social ad campaign, where you know exactly the people you are targeting, you don't want your leads to go through that extra step of a form fill-out. Then the only other solution is Javascript which adds complexity and not everyone has Javascript capabilities on their team. Is there a way for the Munchkin code to pick up the UTM parameters/identify a lead's source and directly feed the information to Marketo?
We need the ability to Edit or Delete an Interesting Moment!
PROBLEM: Our team needs to have the ability to change the Commit Date from the Home area, which isn't possible today. Users have to navigate within the assignment in order to change the Commit Date. The legacy My Work area allows users to update the Commit date.This was previously possible, and we would like that functionality returned; with the new Home area, changing Commit Dates is on a separate page and requires click through and return.Use Case: The team uses the Commit Date to communicate with PMs about when work will actually get done. When the Planned Completion Date and the Commit Date are visible next to each other, and editable next to each other, it's easier (faster) for the user to make date assessments and changes.
Can we autofill hours, so that teams that don't log time can still benefit from Resource Planner?Missing out on Analytics too.
Request for Feature Enhancement (RFE) Summary: One-click support ticket with attached telemetry for CM pipelines that fail after maven and code check stages Use-case: AEM Customers in the support admin role should be able to provide full context including transient environment state for CM and Cloud Service product engineering when a pipeline failure occurs, independent of CSE intervention/ticket triage.When non-deterministic pipeline failures occur, the chain of escalation is Customer -> CSE -> Product Engineer. Invariably, the Product engineer needs to be able to review transient pipeline state in order to be effective in identifying root causes that may or may not originate with product bugs. The escalation process, however, often takes enough time that the transient state is lost due to factors outside the control of the customer or CSE involved in the initial response. Because the identification and collection of the transient state artifacts is easily performed, and perhaps already automated, needing only the pipeline execution Id as an input, it should be possible for an organization user in the support admin role to click a button on the pipeline page when a failure state is reached that triggers the collection and persistence of these artifacts and attaches them to a new support ticket form, prefilled for submission and triage by the CSE. Current/Experienced Behavior: Transient pipeline state including docker containers and internal execution logs are lost if a CSE is not informed in time of the pipeline's execution id in a request for failure dianosis that ultimately requires product engineering support. Improved/Expected Behavior: Organization Support Admin Users should have a one-click pipeline support ticket flow that also triggers immediate capture of transient state Environment Details (AEM version/service pack, any other specifics if applicable): AEM as a Cloud Service Customer-name/Organization name: Change Healthcare Operations LLC. Screenshot (if applicable): Code package (if applicable):
Allow us to make the Planned Completion Date required or at least remove the auto-fill for that day's date. Our users are skipping over this field when submitting a request for work and the requests are coming across looking as though they are due that same day and we are continuously having to reach out to get the correct due date.
As an admin, I'm creating/revising many custom forms. Instead of digging thru our extensive library of custom forms each time I need to edit one, I'd like to be able to pin any custom form especially if I'm building a complex form and in it every day for a while. Right now this is not possible.
Request for Feature Enhancement (RFE) Summary: Would be nice to see in the UI the user who started the pipeline execution Use-case: Sometimes admins need to do audit or troubleshoot pipeline executions. In the case of a situation where a pipeline was triggered unexpectedly it would be good to know who triggered the pipeline so that the necessary actions can be taken like removing access if the user was in a role they shouldn't be in. Current/Experienced Behavior: Currently information on who started the pipeline can only be retrieved using the API on https://www.adobe.io/apis/experiencecloud/cloud-manager/api-reference.html#!AdobeDocs/cloudmanager-api-docs/master/swagger-specs/api.yaml . This would only give the Adobe Identifier which requires another step of finding the email or username either using another API call or by using the admin console to map it back to the username. Improved/Expected Behavior: Show the user name who started execution in the UI of CM interface. Environment Details (AEM version/service pack, any other specifics if applicable): AEM 6.5.8 (AMS) Customer-name/Organization name: Sallie Mae Screenshot (if applicable): Code package (if applicable):
ご担当者様 お世話になります。 弊社の経営層から下記の要望をいただきました。 リードのスコアの推移を見たい！ 例えば、リード A が下記のスコアを保持していたとします。 ・αスコア ・βスコア グラフで指定した期間内において、リードAのスコアがどのように推移しているかをグラフで見たいです。 目的は、複数のキャンペーンを実施したことにより、リードのスコアがどのように変動しているのかを把握したい さらに、複数のリードのスコア推移が見れたら良い。 さらに、同一企業のリードのスコアを累計した企業毎のスコア推移が見れたら良い。
I have a case were we have 800 programs, with one document to send for each. People fill out a form, and go into a program. But, every 6 months, if some programs are still empty, the trigger is desactivated by Marketo. I would like to be able to choose which campaigns / which folders do not have to be desactivated AT ALL.
Straightforward request: I am a big advocate of using Marketo's description fields when using any sort of asset that's in a Marketo tree—a local asset, program, campaign, folder, template, etc. This area allows you to put in key details, link your work back to ticketing systems, provide context for colleagues, and so on. However, as of today you can't search any data that's been put into a description inside the UI. For example, if I wanted to note that a certain Smart Campaign uses the form named A Cool Form with ID 1000, I might put in some text in the description like: "Processes A Cool Form (ID: 1000), assigns values, and sends an alert". However, if a user just searches in the tree for "A Cool Form", they'll only see the actual form asset named "A Cool Form". If the description data was also indexed in the search, the user could see not only the form but all related assets in one go. Could this data get additionally indexed into tree searches?
I am using a Fusion automation to send an update to any user that saves a new task into my main queue project. A checkbox should be added to the Queue Details when it is turned on as a queue to "Disallow new tasks" so that I don't have to be chasing after these users who don't want to save their task conversions into the right project. They should get an error when trying to save the task int a project that disallows new tasks. Anyone else need this? Please vote up. Cheers.
For years, the error message to someone who does not have access to a specific request queue is "This form is currently unavailable". This is just a small ask but can you PLEASE reword this to something that is a little more clear? Many new (and some more experienced) system admins still are fooled by the message and spend some time looking at custom form permissions, which are already convoluted. Rewording this to "You do not have access to this request queue" is more to the point and less confusing for the user and the admins.
Add recipient time zone scheduling to deliveries using recipient's location or explicit preference, e.g. nms:recipient/@timeZone.Deliveries gain another enumerated value in their scheduling time zone dropdown: Recipient time zoneWhen applied, deliveries will stagger sending across target population's timezones. so that everyone gets their emails at the same time on their clocks. E.g. Hawaii and New York recipients will all get their emails at 8 AM.
Description - Allow for creating audiences in the library from other previously saved audience library audiences. Why is this feature important to you - We do a lot of geo targeting and we have custom geo audiences set up for many markets. When we need to combine more that limit will allow (for targeting or for exclusion) we have to basically rebuild them all in one new audience. What a beat down.How would you like the feature to work - When building a new audience in the audience Library allow for the choice of 'rules-based' or 'existing audience'. This would also be great for combining multiple shared AAM audiences or you could have a third option of 'hybrid' that would allow you to combine rules-based logic with existing audiences to create a new audience. Current Behaviour -
We would like to submit an idea that would allow users to see Workfront Proof in Full-screen mode. The full-screen mode would eliminate pin this page gray area and allow a user to take over their entire screen
Description - Recently we shared a read-only workspace report for a critical application with our internal support team. The reason being so that they can monitor this application and proactively start looking into potential issues. By sharing the report with them we had to share access to some analytics components. However, when testing the access it looks like the 'Create Project' option is still available in Workspace. Ideally this could be restricted on certain user groups so that new workspace reports cannot be created by that group. The reason we would like this feature is to avoid non-analytics developers from creating reports that may be misinterpreted. Ideally they are only able to view the reports we choose to grant access to without the ability to create new workspace reports.Why is this feature important to you - Having this feature would help us ensure that workspace reports shared with stakeholders are truly read-only and so that we can restrict curation of analytics reports to developers onlyHow would you like the feature to work - in the admin console, add functionality to restrict user groups (or users) from being able to create new workspace reports when in analysis workspaceCurrent Behaviour - Currently users that are granted access to analysis workspace can create new workspace reports by default
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
