Comments
The same approach could be used to link main assets into a fleet membership to allow the fleet to be moved as a unit even though the relation is not core sub-system, it is an important roster to maintain. For mobile fleets, the use of a functional location to accomplish this is clumsy.This is analogous to the concept of the attachment affiliation.
Just an addition to this in some industries such as animal feeds or weighed items that are dispensed or loaded directly into a cargo vehicle, The qty of the goods are taken from the weighbridge. So they may have agreed to sell 12000Kg but the weighbridge comes in at 12200 - They would need to ship and invoice for 12200. Its an accepted practise within certain industrues.
We used the recommended fields for our business process too. Just removing this feature was a bit unexpected. As i can see we are not the only ones, who used the recommended fields. We would love to see the recommended fields in the new design as well, as it brings a big advantage forr the lead process for example.
I do have the same issue. An admin has to log into the mailbox and share to colleague's personal email every time we receive a S/Mime message. Those attachments can be open in outlook, however they are not supported in CS. We do need to find a solution as we are asking colleagues not to use the mailbox from Outlook, but then we need to go there when we receive those emails from customer.
I do face the same issue. Customer sends an email to two process mailboxes (2 teams) and only shows in one team, i.e. Team 1. Sometimes the query is for Team 2, but it is not visible for Team 2. Others the query should be for Team 1 and Team 2. If Team 2 doesn't see the email as it is not visible in their mailbox queue, the query will be ignored. Not sure what's the best way to manage this emails, but maybe with the capability to change the mailbox queue manually so Team 1 could change it to Team 2?