I am having trouble listing the Work Activity in Approve Time Activities Screen (EP507010). I created some 'Work Item' activities for a case.
I can see those activities in Employee Time Activities Screen (EP307000).
But, whenever I tried to load the case Work Item in Approve Time Activities Screen so that I (Owner of the case or Supervisor of Employee) can't see the Work Item.
I have tried several options such as:
Close the Case
Attach the Case to Project and Contract
Make sure the Case Class is set to Billable
Close the Work Item
etc.
But none of these make it work.
PS: Though it's obvious, I have also made sure the features are set to Enable.
Thank you.
Related
Suppose a user has 2 items in his cart. He goes to another item detail page and clicks buy now. Now, by default, all the two products also add up and go for checkout. My requirement is that when the user clicks buy now, then only that product should proceed and not merge with the other two items in the cart. If the user does not complete the order placement procedure, then it should be added to the cart with the other 2 items. But if he completes the order placement procedure, the other 2 items should stay in the cart.
This is what Flipkart does. Any suggestions in how to achieve this?
Usually, such tasks require a big amount of analytics to find all cases. But a simple plan is:
Create a new button for "Buy now" that will call your own controller/facade/service instead of de.hybris.platform.commerceservices.order.impl.DefaultCommerceCartService#addToCart
Add a new boolean property buyNow to the CartModel
Your new service needs to clean the session from the previous cart. Create a new one with cart.buyNow = true
redirect your customer directly to the checkout
If a customer leaves the checkout or successfully places an order. Clean up all his carts with the buyNow flag. And run a cart restoration process that will return his original cart.
Business requirement is to add a simple action that when an order goes into a Backorder status, a user can click actions > send backorder notification.
I tried to accomplish this via Automation Steps.
Modify existing screen/step
Sales Order enter screen
SO Backorder step
Added action
Name Send Backorder Report
Flow on success do notification
The result was that no option appeared in the menu. I also tried various other steps. At one point the menu option appeared and worked, but then 5 minutes later disappeared
I also tried to do a report instead of an action and set field #reportID and so on as the technical tuesday article describes.
In all cases I am unable to make a simple menu option appear in any status on the sales order screen.
Images
https://www.screencast.com/t/6dTYz4VhB0J1
https://www.screencast.com/t/NeDP2SOEN1e
https://www.screencast.com/t/IQvFMF4KQhl
Is it possible to restrict the purchase order created automatically like when any dropship or special offer item selected in sales order?
I can confirm as of very recent discussions and testing with Netsuite that before submit does not trigger on automatically generated purchase orders.
We have an approvals system in place and were hoping purchase orders could be auto generated and stay pending supervisor approval but this is not possible as the before submit does not trigger.
An enhancement request has been raised by Netsuite for this functionality.
The behaviour of dropship and special order items is dependent on a checkbox. If you clear the checkbox when the order is approved then the automatic POs will not be created.
Checkbox clearing may be done by the user or may be done via a Before Submit user event script on the Sales Order.
If the need to restrict PO creation has something to do with PO vendor characteristics where you may also need to restrict general PO creation then you should extract the vendor check to a library file. that way it could be used in the SO beforeSubmit to clear the createpo flag and the PO beforeSubmit to throw an error.
You could also use the PO After Submit "specialorder" or "dropship" events to check the PO vendor after submit and delete the created PO.
However given your explanation in the comments the SO shouldn't be able to be approved. i.e. why take a drop ship order where the components are not orderable?
I have created a workflow for Sales Orders with 2 states.
State 1: Create Button (before record load)
State 2: Custom Workflow Action
The workflow is set with conditions that the the Sales Orders status is not "Pending Fulfillment". However, there seems to be no rhyme or reason to when the button appears or does not appear. If I change the conditions for the workflow to include pending fulfillment (to add the button) and then revert back, the button is still there.
The workflow doesn't appear to be executing on every load of the Sales Order.
I know this is most likely not enough information, but I can answer questions that people have.
Thanks in advance.
So I built my conditions using the "Visual Binder". When I clicked the radio button for "Formula" it showed me what the visual binder was looking at. It was looking at transaction.statusRef.id instead of transaction.statusRef. When I changed this, the workflow began behaving as I expected.
On CRM in the appointments you can click on the regarding tab to open up that appointments Case details.
Is it possible to add the CASE number for that appointment to the appointments page. Reason being every time I want to see the case number I need to click on regarding tab and open up another webpage.
Would be nice to just have the case number appear on the appointment page, anyway on the page is fine.
Is this possible?
thanks
I agree with Alex and Disagree with Darren, although a plugin would get the job done it seems very excessive for what you are trying to accomplish.
The best way to do this between entities is to use the mapping fields between entity relationships however i don't believe CRM allows this between case and appointment in which case i would create a workflow.
Create a workflow on appointment firing on create or on-change of the regarding field, pull the case number field from the case entity when regarding is on case. This workflow will fire every time this event happens however you can build some extra logic around it and if there isn't a case entity no data will be pulled through.
Hope this helps
You can write a plugin on create and/or update of the regarding field on Appointment. Within this plugin you can check if the regarding field is populated and if so if the entity type is incident. If it is, obtain the Case Number (using the OrganizationService) and set the value of a custom attribute on the triggering Appointment.
Add the custom attribute to the Appointment form. Generally this kind of reference information goes in the header section but it's entirely up to you. If you don't place it there make sure you mark it as read-only.
Depending on your use case you may also want to check in the plugin when the regarding field changes. If the regarding is removed or changed you'll need to make sure you update the case number on the Appointment to reflect this.