Thanks a ton Jason for your superb response.
I am trying to summarize it in detail:-
You created a new DB view & added the custom field for the aging calculation
in it.
After that how to retrieve it in overview console table??
Also even after adding the custom field in the overview console tabl
Thanks a lot Jason for your super detail response.
i believe you are talking about DB view & created a custom view
-"'U__HPD_Help_Desk' DB view" which is accommodating the "zDATEDIFF" with
the aging calculation.
So after that you want that custom - "zDATEDIFF" to be extended on to the
overvi
Thanks LJ for your response.
Please could you elaborate more on the same as you have already achieved it
earlier.
Early response will be highly appreciated.
--
Sent from: http://ars-action-request-system.1.n7.nabble.com/
--
ARSList mailing list
ARSList@arslist.org
https://mailman.rrr.se/cgi/
and I know it's possible to add columns to that tableI know it's
complex, and your workflow will need to be equally complex to accommodate
the complexitiesbut that's how I've done it in the past.
On Tue, Feb 6, 2018 at 12:09 PM, Abhi$hek wrote:
> But LJ the table is overview console tabl
But LJ the table is overview console table only which is a bit complex one
and we need to show the incidents aging in it.
On 06-Feb-2018 11:04 PM, "LJ LongWing" wrote:
> It's not too complicated
>
> 1 - Create a display only field on the form that contains the table field
> 2 - Add that column a
It's not too complicated
1 - Create a display only field on the form that contains the table field
2 - Add that column as a column in the table
3 - Write an AL Guide that loops through the table and does the calculation
needed, and sets the column in the table with the value you want, looping
thro
Can you please provide detail on how to achieve it and show the aging in
the overview console table .
On 06-Feb-2018 10:49 PM, "Dave Shellman" wrote:
> If you need to make the calculation and it needs to be current, the only
> logical trigger is with the table refresh.
>
> Dave
>
> On Tue, Feb 6
If you need to make the calculation and it needs to be current, the only
logical trigger is with the table refresh.
Dave
On Tue, Feb 6, 2018 at 1:29 PM Abhi$hek wrote:
> We can consider simple hours as well.
>
> On 06-Feb-2018 10:02 PM, "Dave Shellman" wrote:
>
>> Sort on Submit Date/Time will
We can consider simple hours as well.
On 06-Feb-2018 10:02 PM, "Dave Shellman" wrote:
> Sort on Submit Date/Time will rank the records which is used in the aging
> calculation.
>
> Should the aging calculation use business time or simple hours open? If
> business time then holidays would need t
Sort on Submit Date/Time will rank the records which is used in the aging
calculation.
Should the aging calculation use business time or simple hours open? If
business time then holidays would need to be considered which leads to
regional holidays in a global environment.
Dave
On Tue, Feb 6, 2
Once case where you can see drastically different out of order Case ID's in
a server group is if Incident(s) are created on a non-user facing admin
server that has been up for a while (months). An example is UDM is used to
create a bunch of request for a project and the admin server is used for
th
Thanks JD for your kind response.
But we need to show the aging in numbers as well so that support staff can
take proper action as per the aging.
On 06-Feb-2018 6:31 PM, "JD Hood" wrote:
> If you just want the incident table sorted in order of older INC's at the
> top, you can sort by incident I
If you just want the incident table sorted in order of older INC's at the
top, you can sort by incident ID# or Submit time and accomplish that. No
workflow or fields needed, just a wee bit of training. Standard column sort
behavior should already work on the table -- click the Inc# column header
to
You could try a table walk on refresh to update all the values in the table.
The only problem would be that the last modified date/time/person are going to
change. Also, could be a nightmare when you have multiple people logged in
trying to update the ticket(s). Not sure if a display only fie
Hi JD,
Thanks for your kind response.
The requirement is just to show the older/aged incidents on top of the
overview console table for the support staff attention only to proactively
manage the SLA.
I can create a custom field in hpd:help desk which will calculate the
DATEDIFF for the submit da
Hi JD,
Thanks for your kind response.
The requirement is just to show the older/aged incidents on top of the
overview console table for the support staff attention only to proactively
manage the SLA.
I can create a custom field in hpd:help desk which will calculate the
DATEDIFF for the submit da
Hi AA,
Presuming I understand correctly and the main point of the business
requirement is to just prioritize the aged incidents first in the Incident
table on the overview console, then couldn't you just sort the table by
Incident Number? Granted with blocks of ID's and a high ticket flow it is
po
17 matches
Mail list logo
