#39536 - 12/27/00 01:16 PM
Table fields
|
Stealth Member
Registered: 06/12/01
Posts: 39
|
I'm not sure if this is possible but I thought I would toss it out and see if anyone has been successful implementing similar functionality.
I have a display only form with two table fields. The one table field on the left is the Available tasks table field that lists all tasks in the application that can be association with a change request (this is a custom application). The other table on the right lists all tasks that have been associated to the current change request. I have two buttons between the two tables, Add >> and << Remove. The Add >> button pushes the highlighted available task in the available tasks table (schema) to the associated tasks to request table (schema). This all works great. The only minor problem is, the users would like to see the task in the available tasks table removed from the list if it exists in the associated tasks to request table. Not sure how to accomplish this. Any ideas or thoughts? The data resides in two separate schemas, Available Tasks and Associated Tasks to Request.
Tamara
---------------------------------------------
Tamara Strang
Ventana Group
tstrang@vengrp.com
www.vengrp.com
(530) 846-6640
(530) 846-6612 FAX
|
|
Top
|
|
|
|
|
|
#39538 - 12/27/00 02:30 PM
Re: Table fields
[Re: matthew willis]
|
Stealth Member
Registered: 06/12/01
Posts: 39
|
I think it is a little more complex that what you proposed. The "Available Tasks" schema is a list of all tasks that a user can choose from when associating tasks to a Change Request. When a user first creates a Change Request there aren't any tasks listed in the "Associated Tasks for Request" table until they add one from the "Available Tasks" table. If the user adds a task from the "Available Tasks" table I push that task to the "Associated Task to Request" schema along with the Request ID for the current Change Request and refresh the "Associated Tasks to Request" table which then displays the task that was pushed. I can't figure out a way to qualify the "Available Tasks" table so it only shows tasks that are not in the "Associated Tasks to Request" table for the current Change Request.
I don't think I can set a flag in the "Available Tasks" table (schema) since there could be concurrent users who need to see all Available Tasks not associated to their current change request. Maybe I am overlooking something or thinking about this too hard.
If you have any more thoughts or need more clarification on my part let me know. Thank you for the quick reply.
Tamara
---- Original Message -----
From: Gidd@Home.COM
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Wednesday, December 27, 2000 11:36 AM
Subject: Re: Table fields
Tamara,
Sounds like you have everything in place. Add an extra selection field called Sent Task to each schema for your purposes. Give it a value of Sent and Unsent
When you push the task from available table set the selection field to Sent value.
In the (Available task) table, change the selection qualification to include 'Sent Task' != "Unsent".
All you have to do now is add a extra Action to the Send Button to refresh the Table AFTER the Push
and bingo the record should not be displayed in Both tables anymore !!
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Tamara Strang
Sent: Wednesday, December 27, 2000 11:16 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Table fields
Hey guys,
I'm not sure if this is possible but I thought I would toss it out and see if anyone has been successful implementing similar functionality.
I have a display only form with two table fields. The one table field on the left is the Available tasks table field that lists all tasks in the application that can be association with a change request (this is a custom application). The other table on the right lists all tasks that have been associated to the current change request. I have two buttons between the two tables, Add >> and << Remove. The Add >> button pushes the highlighted available task in the available tasks table (schema) to the associated tasks to request table (schema). This all works great. The only minor problem is, the users would like to see the task in the available tasks table removed from the list if it exists in the associated tasks to request table. Not sure how to accomplish this. Any ideas or thoughts? The data resides in two separate schemas, Available Tasks and Associated Tasks to Request.
Tamara
---------------------------------------------
Tamara Strang
Ventana Group
tstrang@vengrp.com
www.vengrp.com
(530) 846-6640
(530) 846-6612 FAX
|
|
Top
|
|
|
|
|
|
#39539 - 12/27/00 02:47 PM
Re: Table fields
[Re: matthew willis]
|
Stealth Member
Registered: 06/12/01
Posts: 189
|
To overcome the multi-user problem, you can still use Gidd's solution but instead of setting the 'Sent Task' to "Sent" or "Unsent", set it to either $NULL$ (which should be the defalt value for the field) or to the value of $USER$ - and in your 'Available Task' table, change the selection qualifiation to 'Sent Task' != $USER$.
But then you have another problem, what if the user decided not to continue and closed the form or even closed remedy user??, He won't be able to see all the records stamped with his $USER$ the next time he uses the display-only form. So it's a good idea to add another active link that executes on close window and searches your 'Available Task' form for 'Sent Task'=$USER$ and sets the 'Sent Task' to $NULL$ again.
Hope that helps,
Regards,
Ashraf Elrefaey
Remedy Consultant
Workflow Solutions Ltd
* Phone: +64 4 385 2885
* Cellular: +64 21 377523
* Fax: +64 4 385 2911
* E-Mail: refaey@workflow.co.nz
* Webpage: http://www.workflow.co.nz
-----Original Message-----
From: Tamara Strang [mailto:tstrang@VENGRP.COM]
Sent: Thu, 28 December 2000 09:31
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Gidd,
I think it is a little more complex that what you proposed. The "Available Tasks" schema is a list of all tasks that a user can choose from when associating tasks to a Change Request. When a user first creates a Change Request there aren't any tasks listed in the "Associated Tasks for Request" table until they add one from the "Available Tasks" table. If the user adds a task from the "Available Tasks" table I push that task to the "Associated Task to Request" schema along with the Request ID for the current Change Request and refresh the "Associated Tasks to Request" table which then displays the task that was pushed. I can't figure out a way to qualify the "Available Tasks" table so it only shows tasks that are not in the "Associated Tasks to Request" table for the current Change Request.
I don't think I can set a flag in the "Available Tasks" table (schema) since there could be concurrent users who need to see all Available Tasks not associated to their current change request. Maybe I am overlooking something or thinking about this too hard.
If you have any more thoughts or need more clarification on my part let me know. Thank you for the quick reply.
Tamara
---- Original Message -----
From: Gidd@Home.COM
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Wednesday, December 27, 2000 11:36 AM
Subject: Re: Table fields
Tamara,
Sounds like you have everything in place. Add an extra selection field called Sent Task to each schema for your purposes. Give it a value of Sent and Unsent
When you push the task from available table set the selection field to Sent value.
In the (Available task) table, change the selection qualification to include 'Sent Task' != "Unsent".
All you have to do now is add a extra Action to the Send Button to refresh the Table AFTER the Push
and bingo the record should not be displayed in Both tables anymore !!
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Tamara Strang
Sent: Wednesday, December 27, 2000 11:16 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Table fields
Hey guys,
I'm not sure if this is possible but I thought I would toss it out and see if anyone has been successful implementing similar functionality.
I have a display only form with two table fields. The one table field on the left is the Available tasks table field that lists all tasks in the application that can be association with a change request (this is a custom application). The other table on the right lists all tasks that have been associated to the current change request. I have two buttons between the two tables, Add >> and << Remove. The Add >> button pushes the highlighted available task in the available tasks table (schema) to the associated tasks to request table (schema). This all works great. The only minor problem is, the users would like to see the task in the available tasks table removed from the list if it exists in the associated tasks to request table. Not sure how to accomplish this. Any ideas or thoughts? The data resides in two separate schemas, Available Tasks and Associated Tasks to Request.
Tamara
---------------------------------------------
Tamara Strang
Ventana Group
tstrang@vengrp.com
www.vengrp.com
(530) 846-6640
(530) 846-6612 FAX
|
|
Top
|
|
|
|
|
|
#39540 - 12/27/00 02:56 PM
Re: Table fields
[Re: matthew willis]
|
Stealth Member
Registered: 06/12/01
Posts: 189
|
I forgot to say that the 'Sent Task' field should be a character field rather than being a selection list, sorry!
Regards,
Ashraf Elrefaey
-----Original Message-----
From: Ashraf Elrefaey [mailto:refaey@WORKFLOW.CO.NZ]
Sent: Thu, 28 December 2000 09:48
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Hi Tamara,
To overcome the multi-user problem, you can still use Gidd's solution but instead of setting the 'Sent Task' to "Sent" or "Unsent", set it to either $NULL$ (which should be the defalt value for the field) or to the value of $USER$ - and in your 'Available Task' table, change the selection qualifiation to 'Sent Task' != $USER$.
But then you have another problem, what if the user decided not to continue and closed the form or even closed remedy user??, He won't be able to see all the records stamped with his $USER$ the next time he uses the display-only form. So it's a good idea to add another active link that executes on close window and searches your 'Available Task' form for 'Sent Task'=$USER$ and sets the 'Sent Task' to $NULL$ again.
Hope that helps,
Regards,
Ashraf Elrefaey
Remedy Consultant
Workflow Solutions Ltd
* Phone: +64 4 385 2885
* Cellular: +64 21 377523
* Fax: +64 4 385 2911
* E-Mail: refaey@workflow.co.nz
* Webpage: http://www.workflow.co.nz
-----Original Message-----
From: Tamara Strang [mailto:tstrang@VENGRP.COM]
Sent: Thu, 28 December 2000 09:31
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Gidd,
I think it is a little more complex that what you proposed. The "Available Tasks" schema is a list of all tasks that a user can choose from when associating tasks to a Change Request. When a user first creates a Change Request there aren't any tasks listed in the "Associated Tasks for Request" table until they add one from the "Available Tasks" table. If the user adds a task from the "Available Tasks" table I push that task to the "Associated Task to Request" schema along with the Request ID for the current Change Request and refresh the "Associated Tasks to Request" table which then displays the task that was pushed. I can't figure out a way to qualify the "Available Tasks" table so it only shows tasks that are not in the "Associated Tasks to Request" table for the current Change Request.
I don't think I can set a flag in the "Available Tasks" table (schema) since there could be concurrent users who need to see all Available Tasks not associated to their current change request. Maybe I am overlooking something or thinking about this too hard.
If you have any more thoughts or need more clarification on my part let me know. Thank you for the quick reply.
Tamara
---- Original Message -----
From: Gidd@Home.COM
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Wednesday, December 27, 2000 11:36 AM
Subject: Re: Table fields
Tamara,
Sounds like you have everything in place. Add an extra selection field called Sent Task to each schema for your purposes. Give it a value of Sent and Unsent
When you push the task from available table set the selection field to Sent value.
In the (Available task) table, change the selection qualification to include 'Sent Task' != "Unsent".
All you have to do now is add a extra Action to the Send Button to refresh the Table AFTER the Push
and bingo the record should not be displayed in Both tables anymore !!
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Tamara Strang
Sent: Wednesday, December 27, 2000 11:16 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Table fields
Hey guys,
I'm not sure if this is possible but I thought I would toss it out and see if anyone has been successful implementing similar functionality.
I have a display only form with two table fields. The one table field on the left is the Available tasks table field that lists all tasks in the application that can be association with a change request (this is a custom application). The other table on the right lists all tasks that have been associated to the current change request. I have two buttons between the two tables, Add >> and << Remove. The Add >> button pushes the highlighted available task in the available tasks table (schema) to the associated tasks to request table (schema). This all works great. The only minor problem is, the users would like to see the task in the available tasks table removed from the list if it exists in the associated tasks to request table. Not sure how to accomplish this. Any ideas or thoughts? The data resides in two separate schemas, Available Tasks and Associated Tasks to Request.
Tamara
---------------------------------------------
Tamara Strang
Ventana Group
tstrang@vengrp.com
www.vengrp.com
(530) 846-6640
(530) 846-6612 FAX
|
|
Top
|
|
|
|
|
|
#39541 - 12/27/00 03:24 PM
Re: Table fields
[Re: matthew willis]
|
Stealth Member
Registered: 06/12/01
Posts: 39
|
Tamara
----- Original Message -----
From: Ashraf Elrefaey
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Wednesday, December 27, 2000 12:56 PM
Subject: Re: Table fields
Hi Tamara,
I forgot to say that the 'Sent Task' field should be a character field rather than being a selection list, sorry!
Regards,
Ashraf Elrefaey
-----Original Message-----
From: Ashraf Elrefaey [mailto:refaey@WORKFLOW.CO.NZ]
Sent: Thu, 28 December 2000 09:48
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Hi Tamara,
To overcome the multi-user problem, you can still use Gidd's solution but instead of setting the 'Sent Task' to "Sent" or "Unsent", set it to either $NULL$ (which should be the defalt value for the field) or to the value of $USER$ - and in your 'Available Task' table, change the selection qualifiation to 'Sent Task' != $USER$.
But then you have another problem, what if the user decided not to continue and closed the form or even closed remedy user??, He won't be able to see all the records stamped with his $USER$ the next time he uses the display-only form. So it's a good idea to add another active link that executes on close window and searches your 'Available Task' form for 'Sent Task'=$USER$ and sets the 'Sent Task' to $NULL$ again.
Hope that helps,
Regards,
Ashraf Elrefaey
Remedy Consultant
Workflow Solutions Ltd
* Phone: +64 4 385 2885
* Cellular: +64 21 377523
* Fax: +64 4 385 2911
* E-Mail: refaey@workflow.co.nz
* Webpage: http://www.workflow.co.nz
-----Original Message-----
From: Tamara Strang [mailto:tstrang@VENGRP.COM]
Sent: Thu, 28 December 2000 09:31
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Gidd,
I think it is a little more complex that what you proposed. The "Available Tasks" schema is a list of all tasks that a user can choose from when associating tasks to a Change Request. When a user first creates a Change Request there aren't any tasks listed in the "Associated Tasks for Request" table until they add one from the "Available Tasks" table. If the user adds a task from the "Available Tasks" table I push that task to the "Associated Task to Request" schema along with the Request ID for the current Change Request and refresh the "Associated Tasks to Request" table which then displays the task that was pushed. I can't figure out a way to qualify the "Available Tasks" table so it only shows tasks that are not in the "Associated Tasks to Request" table for the current Change Request.
I don't think I can set a flag in the "Available Tasks" table (schema) since there could be concurrent users who need to see all Available Tasks not associated to their current change request. Maybe I am overlooking something or thinking about this too hard.
If you have any more thoughts or need more clarification on my part let me know. Thank you for the quick reply.
Tamara
---- Original Message -----
From: Gidd@Home.COM
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Wednesday, December 27, 2000 11:36 AM
Subject: Re: Table fields
Tamara,
Sounds like you have everything in place. Add an extra selection field called Sent Task to each schema for your purposes. Give it a value of Sent and Unsent
When you push the task from available table set the selection field to Sent value.
In the (Available task) table, change the selection qualification to include 'Sent Task' != "Unsent".
All you have to do now is add a extra Action to the Send Button to refresh the Table AFTER the Push
and bingo the record should not be displayed in Both tables anymore !!
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Tamara Strang
Sent: Wednesday, December 27, 2000 11:16 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Table fields
Hey guys,
I'm not sure if this is possible but I thought I would toss it out and see if anyone has been successful implementing similar functionality.
I have a display only form with two table fields. The one table field on the left is the Available tasks table field that lists all tasks in the application that can be association with a change request (this is a custom application). The other table on the right lists all tasks that have been associated to the current change request. I have two buttons between the two tables, Add >> and << Remove. The Add >> button pushes the highlighted available task in the available tasks table (schema) to the associated tasks to request table (schema). This all works great. The only minor problem is, the users would like to see the task in the available tasks table removed from the list if it exists in the associated tasks to request table. Not sure how to accomplish this. Any ideas or thoughts? The data resides in two separate schemas, Available Tasks and Associated Tasks to Request.
Tamara
---------------------------------------------
Tamara Strang
Ventana Group
tstrang@vengrp.com
www.vengrp.com
(530) 846-6640
(530) 846-6612 FAX
|
|
Top
|
|
|
|
|
|
#39542 - 12/27/00 06:21 PM
Re: Table fields
[Re: matthew willis]
|
Old Hand
Registered: 06/12/01
Posts: 2103
Loc: California
|
You on good form today !! Does she need/want the ability to add it to one form and then have a change of
mind and put it back where it was? Is there a business rule here ? Easy fix. Like your suggestion.
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Ashraf Elrefaey
Sent: Wednesday, December 27, 2000 12:48 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Hi Tamara,
To overcome the multi-user problem, you can still use Gidd's solution but instead of setting the 'Sent Task' to "Sent" or "Unsent", set it to either $NULL$ (which should be the defalt value for the field) or to the value of $USER$ - and in your 'Available Task' table, change the selection qualifiation to 'Sent Task' != $USER$.
But then you have another problem, what if the user decided not to continue and closed the form or even closed remedy user??, He won't be able to see all the records stamped with his $USER$ the next time he uses the display-only form. So it's a good idea to add another active link that executes on close window and searches your 'Available Task' form for 'Sent Task'=$USER$ and sets the 'Sent Task' to $NULL$ again.
Hope that helps,
Regards,
Ashraf Elrefaey
Remedy Consultant
Workflow Solutions Ltd
* Phone: +64 4 385 2885
* Cellular: +64 21 377523
* Fax: +64 4 385 2911
* E-Mail: refaey@workflow.co.nz
* Webpage: http://www.workflow.co.nz
-----Original Message-----
From: Tamara Strang [mailto:tstrang@VENGRP.COM]
Sent: Thu, 28 December 2000 09:31
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Gidd,
I think it is a little more complex that what you proposed. The "Available Tasks" schema is a list of all tasks that a user can choose from when associating tasks to a Change Request. When a user first creates a Change Request there aren't any tasks listed in the "Associated Tasks for Request" table until they add one from the "Available Tasks" table. If the user adds a task from the "Available Tasks" table I push that task to the "Associated Task to Request" schema along with the Request ID for the current Change Request and refresh the "Associated Tasks to Request" table which then displays the task that was pushed. I can't figure out a way to qualify the "Available Tasks" table so it only shows tasks that are not in the "Associated Tasks to Request" table for the current Change Request.
I don't think I can set a flag in the "Available Tasks" table (schema) since there could be concurrent users who need to see all Available Tasks not associated to their current change request. Maybe I am overlooking something or thinking about this too hard.
If you have any more thoughts or need more clarification on my part let me know. Thank you for the quick reply.
Tamara
---- Original Message -----
From: Gidd@Home.COM
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Wednesday, December 27, 2000 11:36 AM
Subject: Re: Table fields
Tamara,
Sounds like you have everything in place. Add an extra selection field called Sent Task to each schema for your purposes. Give it a value of Sent and Unsent
When you push the task from available table set the selection field to Sent value.
In the (Available task) table, change the selection qualification to include 'Sent Task' != "Unsent".
All you have to do now is add a extra Action to the Send Button to refresh the Table AFTER the Push
and bingo the record should not be displayed in Both tables anymore !!
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Tamara Strang
Sent: Wednesday, December 27, 2000 11:16 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Table fields
Hey guys,
I'm not sure if this is possible but I thought I would toss it out and see if anyone has been successful implementing similar functionality.
I have a display only form with two table fields. The one table field on the left is the Available tasks table field that lists all tasks in the application that can be association with a change request (this is a custom application). The other table on the right lists all tasks that have been associated to the current change request. I have two buttons between the two tables, Add >> and << Remove. The Add >> button pushes the highlighted available task in the available tasks table (schema) to the associated tasks to request table (schema). This all works great. The only minor problem is, the users would like to see the task in the available tasks table removed from the list if it exists in the associated tasks to request table. Not sure how to accomplish this. Any ideas or thoughts? The data resides in two separate schemas, Available Tasks and Associated Tasks to Request.
Tamara
---------------------------------------------
Tamara Strang
Ventana Group
tstrang@vengrp.com
www.vengrp.com
(530) 846-6640
(530) 846-6612 FAX
|
|
Top
|
|
|
|
|
|
#39543 - 12/27/00 07:07 PM
Re: Table fields
[Re: matthew willis]
|
Stealth Member
Registered: 06/12/01
Posts: 189
|
It's another beautiful day (with apologies to U2).
Regards,
Ashraf Elrefaey
Remedy Consultant
Workflow Solutions Ltd
* Phone: +64 4 385 2885
* Cellular: +64 21 377523
* Fax: +64 4 385 2911
* E-Mail: mailto:refaey@workflow.co.nz
* Webpage: http://www.workflow.co.nz
-----Original Message-----
From: Gidd@Home.COM [mailto:gidd@HOME.COM]
Sent: Thu, 28 December 2000 13:22
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Ash,
You on good form today !! Does she need/want the ability to add it to one form and then have a change of
mind and put it back where it was? Is there a business rule here ? Easy fix. Like your suggestion.
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Ashraf Elrefaey
Sent: Wednesday, December 27, 2000 12:48 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Hi Tamara,
To overcome the multi-user problem, you can still use Gidd's solution but instead of setting the 'Sent Task' to "Sent" or "Unsent", set it to either $NULL$ (which should be the defalt value for the field) or to the value of $USER$ - and in your 'Available Task' table, change the selection qualifiation to 'Sent Task' != $USER$.
But then you have another problem, what if the user decided not to continue and closed the form or even closed remedy user??, He won't be able to see all the records stamped with his $USER$ the next time he uses the display-only form. So it's a good idea to add another active link that executes on close window and searches your 'Available Task' form for 'Sent Task'=$USER$ and sets the 'Sent Task' to $NULL$ again.
Hope that helps,
Regards,
Ashraf Elrefaey
Remedy Consultant
Workflow Solutions Ltd
* Phone: +64 4 385 2885
* Cellular: +64 21 377523
* Fax: +64 4 385 2911
* E-Mail: refaey@workflow.co.nz
* Webpage: http://www.workflow.co.nz
-----Original Message-----
From: Tamara Strang [mailto:tstrang@VENGRP.COM]
Sent: Thu, 28 December 2000 09:31
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Gidd,
I think it is a little more complex that what you proposed. The "Available Tasks" schema is a list of all tasks that a user can choose from when associating tasks to a Change Request. When a user first creates a Change Request there aren't any tasks listed in the "Associated Tasks for Request" table until they add one from the "Available Tasks" table. If the user adds a task from the "Available Tasks" table I push that task to the "Associated Task to Request" schema along with the Request ID for the current Change Request and refresh the "Associated Tasks to Request" table which then displays the task that was pushed. I can't figure out a way to qualify the "Available Tasks" table so it only shows tasks that are not in the "Associated Tasks to Request" table for the current Change Request.
I don't think I can set a flag in the "Available Tasks" table (schema) since there could be concurrent users who need to see all Available Tasks not associated to their current change request. Maybe I am overlooking something or thinking about this too hard.
If you have any more thoughts or need more clarification on my part let me know. Thank you for the quick reply.
Tamara
---- Original Message -----
From: Gidd@Home.COM
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Wednesday, December 27, 2000 11:36 AM
Subject: Re: Table fields
Tamara,
Sounds like you have everything in place. Add an extra selection field called Sent Task to each schema for your purposes. Give it a value of Sent and Unsent
When you push the task from available table set the selection field to Sent value.
In the (Available task) table, change the selection qualification to include 'Sent Task' != "Unsent".
All you have to do now is add a extra Action to the Send Button to refresh the Table AFTER the Push
and bingo the record should not be displayed in Both tables anymore !!
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Tamara Strang
Sent: Wednesday, December 27, 2000 11:16 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Table fields
Hey guys,
I'm not sure if this is possible but I thought I would toss it out and see if anyone has been successful implementing similar functionality.
I have a display only form with two table fields. The one table field on the left is the Available tasks table field that lists all tasks in the application that can be association with a change request (this is a custom application). The other table on the right lists all tasks that have been associated to the current change request. I have two buttons between the two tables, Add >> and << Remove. The Add >> button pushes the highlighted available task in the available tasks table (schema) to the associated tasks to request table (schema). This all works great. The only minor problem is, the users would like to see the task in the available tasks table removed from the list if it exists in the associated tasks to request table. Not sure how to accomplish this. Any ideas or thoughts? The data resides in two separate schemas, Available Tasks and Associated Tasks to Request.
Tamara
---------------------------------------------
Tamara Strang
Ventana Group
tstrang@vengrp.com
www.vengrp.com
(530) 846-6640
(530) 846-6612 FAX
|
|
Top
|
|
|
|
|
|
#39544 - 12/27/00 08:59 PM
Re: Table fields
[Re: matthew willis]
|
Old Hand
Registered: 06/12/01
Posts: 2103
Loc: California
|
Sure it is summer down under, it's bloody winter here !!
Happy New Year to all my friends at WFA !!
Regards...Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Ashraf Elrefaey
Sent: Wednesday, December 27, 2000 5:08 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Hi Gidd,
It's another beautiful day (with apologies to U2).
Regards,
Ashraf Elrefaey
Remedy Consultant
Workflow Solutions Ltd
* Phone: +64 4 385 2885
* Cellular: +64 21 377523
* Fax: +64 4 385 2911
* E-Mail: mailto:refaey@workflow.co.nz
* Webpage: http://www.workflow.co.nz
-----Original Message-----
From: Gidd@Home.COM [mailto:gidd@HOME.COM]
Sent: Thu, 28 December 2000 13:22
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Ash,
You on good form today !! Does she need/want the ability to add it to one form and then have a change of
mind and put it back where it was? Is there a business rule here ? Easy fix. Like your suggestion.
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Ashraf Elrefaey
Sent: Wednesday, December 27, 2000 12:48 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Hi Tamara,
To overcome the multi-user problem, you can still use Gidd's solution but instead of setting the 'Sent Task' to "Sent" or "Unsent", set it to either $NULL$ (which should be the defalt value for the field) or to the value of $USER$ - and in your 'Available Task' table, change the selection qualifiation to 'Sent Task' != $USER$.
But then you have another problem, what if the user decided not to continue and closed the form or even closed remedy user??, He won't be able to see all the records stamped with his $USER$ the next time he uses the display-only form. So it's a good idea to add another active link that executes on close window and searches your 'Available Task' form for 'Sent Task'=$USER$ and sets the 'Sent Task' to $NULL$ again.
Hope that helps,
Regards,
Ashraf Elrefaey
Remedy Consultant
Workflow Solutions Ltd
* Phone: +64 4 385 2885
* Cellular: +64 21 377523
* Fax: +64 4 385 2911
* E-Mail: refaey@workflow.co.nz
* Webpage: http://www.workflow.co.nz
-----Original Message-----
From: Tamara Strang [mailto:tstrang@VENGRP.COM]
Sent: Thu, 28 December 2000 09:31
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Gidd,
I think it is a little more complex that what you proposed. The "Available Tasks" schema is a list of all tasks that a user can choose from when associating tasks to a Change Request. When a user first creates a Change Request there aren't any tasks listed in the "Associated Tasks for Request" table until they add one from the "Available Tasks" table. If the user adds a task from the "Available Tasks" table I push that task to the "Associated Task to Request" schema along with the Request ID for the current Change Request and refresh the "Associated Tasks to Request" table which then displays the task that was pushed. I can't figure out a way to qualify the "Available Tasks" table so it only shows tasks that are not in the "Associated Tasks to Request" table for the current Change Request.
I don't think I can set a flag in the "Available Tasks" table (schema) since there could be concurrent users who need to see all Available Tasks not associated to their current change request. Maybe I am overlooking something or thinking about this too hard.
If you have any more thoughts or need more clarification on my part let me know. Thank you for the quick reply.
Tamara
---- Original Message -----
From: Gidd@Home.COM
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Wednesday, December 27, 2000 11:36 AM
Subject: Re: Table fields
Tamara,
Sounds like you have everything in place. Add an extra selection field called Sent Task to each schema for your purposes. Give it a value of Sent and Unsent
When you push the task from available table set the selection field to Sent value.
In the (Available task) table, change the selection qualification to include 'Sent Task' != "Unsent".
All you have to do now is add a extra Action to the Send Button to refresh the Table AFTER the Push
and bingo the record should not be displayed in Both tables anymore !!
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Tamara Strang
Sent: Wednesday, December 27, 2000 11:16 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Table fields
Hey guys,
I'm not sure if this is possible but I thought I would toss it out and see if anyone has been successful implementing similar functionality.
I have a display only form with two table fields. The one table field on the left is the Available tasks table field that lists all tasks in the application that can be association with a change request (this is a custom application). The other table on the right lists all tasks that have been associated to the current change request. I have two buttons between the two tables, Add >> and << Remove. The Add >> button pushes the highlighted available task in the available tasks table (schema) to the associated tasks to request table (schema). This all works great. The only minor problem is, the users would like to see the task in the available tasks table removed from the list if it exists in the associated tasks to request table. Not sure how to accomplish this. Any ideas or thoughts? The data resides in two separate schemas, Available Tasks and Associated Tasks to Request.
Tamara
---------------------------------------------
Tamara Strang
Ventana Group
tstrang@vengrp.com
www.vengrp.com
(530) 846-6640
(530) 846-6612 FAX
|
|
Top
|
|
|
|
|
|
#39545 - 12/28/00 08:21 AM
Re: Table fields
[Re: matthew willis]
|
Stealth Member
Registered: 06/12/01
Posts: 61
|
Mark A. Worley
SAIC (HQAFWA)
(402) 294-8226
Mark.Worley@afwa.af.mil < mailto:Mark.Worley@afwa.af.mil>
-----Original Message-----
From: Tamara Strang [mailto:tstrang@VENGRP.COM]
Sent: Wednesday, December 27, 2000 15:25 C
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Thank you for all the replies. I will try the $USER$ approach. I think it will work.
Tamara
----- Original Message -----
From: Ashraf Elrefaey
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Wednesday, December 27, 2000 12:56 PM
Subject: Re: Table fields
Hi Tamara,
I forgot to say that the 'Sent Task' field should be a character field rather than being a selection list, sorry!
Regards,
Ashraf Elrefaey
-----Original Message-----
From: Ashraf Elrefaey [mailto:refaey@WORKFLOW.CO.NZ]
Sent: Thu, 28 December 2000 09:48
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Hi Tamara,
To overcome the multi-user problem, you can still use Gidd's solution but instead of setting the 'Sent Task' to "Sent" or "Unsent", set it to either $NULL$ (which should be the defalt value for the field) or to the value of $USER$ - and in your 'Available Task' table, change the selection qualifiation to 'Sent Task' != $USER$.
But then you have another problem, what if the user decided not to continue and closed the form or even closed remedy user??, He won't be able to see all the records stamped with his $USER$ the next time he uses the display-only form. So it's a good idea to add another active link that executes on close window and searches your 'Available Task' form for 'Sent Task'=$USER$ and sets the 'Sent Task' to $NULL$ again.
Hope that helps,
Regards,
Ashraf Elrefaey
Remedy Consultant
Workflow Solutions Ltd
* Phone: +64 4 385 2885
* Cellular: +64 21 377523
* Fax: +64 4 385 2911
* E-Mail: refaey@workflow.co.nz
* Webpage: http://www.workflow.co.nz
-----Original Message-----
From: Tamara Strang [mailto:tstrang@VENGRP.COM]
Sent: Thu, 28 December 2000 09:31
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Table fields
Gidd,
I think it is a little more complex that what you proposed. The "Available Tasks" schema is a list of all tasks that a user can choose from when associating tasks to a Change Request. When a user first creates a Change Request there aren't any tasks listed in the "Associated Tasks for Request" table until they add one from the "Available Tasks" table. If the user adds a task from the "Available Tasks" table I push that task to the "Associated Task to Request" schema along with the Request ID for the current Change Request and refresh the "Associated Tasks to Request" table which then displays the task that was pushed. I can't figure out a way to qualify the "Available Tasks" table so it only shows tasks that are not in the "Associated Tasks to Request" table for the current Change Request.
I don't think I can set a flag in the "Available Tasks" table (schema) since there could be concurrent users who need to see all Available Tasks not associated to their current change request. Maybe I am overlooking something or thinking about this too hard.
If you have any more thoughts or need more clarification on my part let me know. Thank you for the quick reply.
Tamara
---- Original Message -----
From: Gidd@Home.COM
To: ARSLIST@LISTSERV.VISTAIT.COM
Sent: Wednesday, December 27, 2000 11:36 AM
Subject: Re: Table fields
Tamara,
Sounds like you have everything in place. Add an extra selection field called Sent Task to each schema for your purposes. Give it a value of Sent and Unsent
When you push the task from available table set the selection field to Sent value.
In the (Available task) table, change the selection qualification to include 'Sent Task' != "Unsent".
All you have to do now is add a extra Action to the Send Button to refresh the Table AFTER the Push
and bingo the record should not be displayed in Both tables anymore !!
Gidd
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Tamara Strang
Sent: Wednesday, December 27, 2000 11:16 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Table fields
Hey guys,
I'm not sure if this is possible but I thought I would toss it out and see if anyone has been successful implementing similar functionality.
I have a display only form with two table fields. The one table field on the left is the Available tasks table field that lists all tasks in the application that can be association with a change request (this is a custom application). The other table on the right lists all tasks that have been associated to the current change request. I have two buttons between the two tables, Add >> and << Remove. The Add >> button pushes the highlighted available task in the available tasks table (schema) to the associated tasks to request table (schema). This all works great. The only minor problem is, the users would like to see the task in the available tasks table removed from the list if it exists in the associated tasks to request table. Not sure how to accomplish this. Any ideas or thoughts? The data resides in two separate schemas, Available Tasks and Associated Tasks to Request.
Tamara
---------------------------------------------
Tamara Strang
Ventana Group
tstrang@vengrp.com
www.vengrp.com
(530) 846-6640
(530) 846-6612 FAX
|
|
Top
|
|
|
|
|
|
|
Previous Topic
Index