I'm building an application that has a number of clients allocated to a
community worker that are to be presented in the case list in the "to be
visited order", essentially a crude route plan. I've added a sequence field
as the first field in the case list which works fine with a static list.
However my problem comes when a new client gets added. I could manually
modify the sequence field of all the clients below the inserted newcomer
but with potentially a 1000 clients this isn't practical.
My question is:- How can I re-index the sequence field so that the "to be
visited" order is updated automatically?
How are you calculating the visit sequence? Is it a local algorithm based
on priority/urgency/last visit, or is it a global algorithm that needs to
be aware of all of the clients in order to determine the order?
We're working on exposing the functionality in the case list builder to
sort by multiple field comparisons, which may make this easier. That would
allow you to, say, compare 3 different fields with different priorities to
build the sorted table, rather than try to build that comparison statically.
-Clayton
···
On Fri, Jun 14, 2013 at 10:23 AM, MickT wrote:
Hi All, need some help please,
I'm building an application that has a number of clients allocated to a
community worker that are to be presented in the case list in the "to be
visited order", essentially a crude route plan. I've added a sequence field
as the first field in the case list which works fine with a static list.
However my problem comes when a new client gets added. I could manually
modify the sequence field of all the clients below the inserted newcomer
but with potentially a 1000 clients this isn't practical.
My question is:- How can I re-index the sequence field so that the "to be
visited" order is updated automatically?
The scenario is that the clients (1,000+) are split into a number of
rounds. Each round has approx. 50 clients each, though this is never static
as clients drop off for various reasons and new clients are added on a
daily basis. The clients are never closed unless they pass away, as they
may come back into the list based on their requirements at a future time, I
have a flag that marks them active/inactive and can include or exclude by
using a filter. Each round covers a specific geographical area so the
sequence they appear on the case list is the sequence they would be
visited. In a perfect world I guess some sort of GPS route planner would be
used but that is not a practical solution in this project due to the cost
and complexity.
Sequencing at the moment is done by having a text field as the first field
in the case list and entering an alpha-numeric value against each of the
clients. Using this technique I can correctly sequence the small number of
clients within the pilot project. However two issues arise,
New clients are added by admin staff who in conjunction with the
community staff are familiar with the locations and can manually place the
new client within the sequence correctly, I then need a method to get all
the subsequent client positions re-indexed to reflect their revised
position automatically, and second
When the full project implementation is running the sequencing will
have to consider two fields, the roundID and the sequence within that round.
The proposed facility you mention would seem to be the answer to this
issue, I guess the million dollar question is what time frame have you in
mind for a release. I'm happy to be a test site if an early release is
available.
Best Regards
Mick
···
On Friday, 14 June 2013 15:23:08 UTC+1, MickT wrote:
>
> Hi All, need some help please,
>
> I'm building an application that has a number of clients allocated to a
> community worker that are to be presented in the case list in the "to be
> visited order", essentially a crude route plan. I've added a sequence field
> as the first field in the case list which works fine with a static list.
>
> However my problem comes when a new client gets added. I could manually
> modify the sequence field of all the clients below the inserted newcomer
> but with potentially a 1000 clients this isn't practical.
>
> My question is:- How can I re-index the sequence field so that the "to be
> visited" order is updated automatically?
>
> All and any suggestions appreciated
>
> Regards
>
> Mick
>
We're aiming to have sorting on multiple items in the case list available
sometime this July. We'll keep you updated on progress and thanks for the
offer to help us test an early release!
Thanks,
Amelia
···
On Mon, Jun 17, 2013 at 4:18 AM, MickT wrote:
Hi Clayton,
Appreciate your response so promptly.
The scenario is that the clients (1,000+) are split into a number of
rounds. Each round has approx. 50 clients each, though this is never static
as clients drop off for various reasons and new clients are added on a
daily basis. The clients are never closed unless they pass away, as they
may come back into the list based on their requirements at a future time, I
have a flag that marks them active/inactive and can include or exclude by
using a filter. Each round covers a specific geographical area so the
sequence they appear on the case list is the sequence they would be
visited. In a perfect world I guess some sort of GPS route planner would be
used but that is not a practical solution in this project due to the cost
and complexity.
Sequencing at the moment is done by having a text field as the first field
in the case list and entering an alpha-numeric value against each of the
clients. Using this technique I can correctly sequence the small number of
clients within the pilot project. However two issues arise,
New clients are added by admin staff who in conjunction with the
community staff are familiar with the locations and can manually place the
new client within the sequence correctly, I then need a method to get all
the subsequent client positions re-indexed to reflect their revised
position automatically, and second
When the full project implementation is running the sequencing will
have to consider two fields, the roundID and the sequence within that round.
The proposed facility you mention would seem to be the answer to this
issue, I guess the million dollar question is what time frame have you in
mind for a release. I'm happy to be a test site if an early release is
available.
Best Regards
Mick
On Friday, 14 June 2013 15:23:08 UTC+1, MickT wrote:
Hi All, need some help please,
I'm building an application that has a number of clients allocated to a
community worker that are to be presented in the case list in the "to be
visited order", essentially a crude route plan. I've added a sequence field
as the first field in the case list which works fine with a static list.
However my problem comes when a new client gets added. I could manually
modify the sequence field of all the clients below the inserted newcomer
but with potentially a 1000 clients this isn't practical.
My question is:- How can I re-index the sequence field so that the "to be
visited" order is updated automatically?