You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by Adrian Crum <ad...@hlmksw.com> on 2008/06/09 19:45:02 UTC
Question About The Asset Maintenance Component
I have expanded the functionality of Asset Maintenance. Currently,
maintenance tasks are assigned automatically to the logged-in user and
there is no way to change it or assign the task to someone else. I have
added the ability to assign maintenance tasks to someone else.
The assignment requires a party role. Presenting the user with a list of
all roles to pick from is not user-friendly because the list is quite
long. I would like to have a smaller list that is more Fixed Asset
Maintenance specific. I'm not sure how I should implement the smaller
role list.
I'm thinking the list should contain three roles: an outside service, a
maintenance manager, and a maintenance worker. Should I use existing
roles, or create new ones?
Another idea is to populate the list with parties/roles that are already
related to the fixed asset in question.
Any advice would be appreciated!
-Adrian
Re: Question About The Asset Maintenance Component
Posted by Anil Patel <an...@hotwaxmedia.com>.
Cool that will be so good.
Regards
Anil Patel
On Jun 9, 2008, at 6:45 PM, Adrian Crum wrote:
> Anil,
>
> When I'm finished with the component it will be much improved. I'm
> also working on having the workefforts updated via incoming email -
> so maintenance workers can update their tasks via cell phone. When
> it's all done, you should check it out.
>
> -Adrian
>
> Anil Patel wrote:
>> I did same thing when I implemented for my previous employer.
>> Regards
>> Anil Patel
>> On Jun 9, 2008, at 3:02 PM, Adrian Crum wrote:
>>> David E Jones wrote:
>>>> I can think of two main ways of doing this:
>>>> 1. list explicitly/inline the roles you want to show (instead of
>>>> doing a query)
>>>> 2. create a parent role and put the roles you want under it and
>>>> query by the parent ID
>>>
>>> I like idea #2. Using that approach, a user could expand the list
>>> just by adding child roles.
>>>
>>>> As for which roles to use, and whether to create or not, it's
>>>> totally okay to add new roles but you might consider keeping the
>>>> roles used more general and use ideas like "manager" and
>>>> "worker" (or assignee, performer, whatever) instead of very
>>>> specific ones.
>>>
>>> I was planning on keeping it as generic as possible.
>>>
>>> Thank you for the advice!
>>>
>>> -Adrian
>>>
>>>
>>>> On Jun 9, 2008, at 11:45 AM, Adrian Crum wrote:
>>>>> I have expanded the functionality of Asset Maintenance.
>>>>> Currently, maintenance tasks are assigned automatically to the
>>>>> logged-in user and there is no way to change it or assign the
>>>>> task to someone else. I have added the ability to assign
>>>>> maintenance tasks to someone else.
>>>>>
>>>>> The assignment requires a party role. Presenting the user with a
>>>>> list of all roles to pick from is not user-friendly because the
>>>>> list is quite long. I would like to have a smaller list that is
>>>>> more Fixed Asset Maintenance specific. I'm not sure how I should
>>>>> implement the smaller role list.
>>>>>
>>>>> I'm thinking the list should contain three roles: an outside
>>>>> service, a maintenance manager, and a maintenance worker. Should
>>>>> I use existing roles, or create new ones?
>>>>>
>>>>> Another idea is to populate the list with parties/roles that are
>>>>> already related to the fixed asset in question.
>>>>>
>>>>> Any advice would be appreciated!
>>>>>
>>>>> -Adrian
Re: Question About The Asset Maintenance Component
Posted by Adrian Crum <ad...@hlmksw.com>.
Anil,
When I'm finished with the component it will be much improved. I'm also
working on having the workefforts updated via incoming email - so
maintenance workers can update their tasks via cell phone. When it's all
done, you should check it out.
-Adrian
Anil Patel wrote:
> I did same thing when I implemented for my previous employer.
>
> Regards
> Anil Patel
>
> On Jun 9, 2008, at 3:02 PM, Adrian Crum wrote:
>
>> David E Jones wrote:
>>> I can think of two main ways of doing this:
>>> 1. list explicitly/inline the roles you want to show (instead of
>>> doing a query)
>>> 2. create a parent role and put the roles you want under it and query
>>> by the parent ID
>>
>> I like idea #2. Using that approach, a user could expand the list just
>> by adding child roles.
>>
>>> As for which roles to use, and whether to create or not, it's totally
>>> okay to add new roles but you might consider keeping the roles used
>>> more general and use ideas like "manager" and "worker" (or assignee,
>>> performer, whatever) instead of very specific ones.
>>
>> I was planning on keeping it as generic as possible.
>>
>> Thank you for the advice!
>>
>> -Adrian
>>
>>
>>> On Jun 9, 2008, at 11:45 AM, Adrian Crum wrote:
>>>> I have expanded the functionality of Asset Maintenance. Currently,
>>>> maintenance tasks are assigned automatically to the logged-in user
>>>> and there is no way to change it or assign the task to someone else.
>>>> I have added the ability to assign maintenance tasks to someone else.
>>>>
>>>> The assignment requires a party role. Presenting the user with a
>>>> list of all roles to pick from is not user-friendly because the list
>>>> is quite long. I would like to have a smaller list that is more
>>>> Fixed Asset Maintenance specific. I'm not sure how I should
>>>> implement the smaller role list.
>>>>
>>>> I'm thinking the list should contain three roles: an outside
>>>> service, a maintenance manager, and a maintenance worker. Should I
>>>> use existing roles, or create new ones?
>>>>
>>>> Another idea is to populate the list with parties/roles that are
>>>> already related to the fixed asset in question.
>>>>
>>>> Any advice would be appreciated!
>>>>
>>>> -Adrian
>
Re: Question About The Asset Maintenance Component
Posted by Anil Patel <an...@hotwaxmedia.com>.
I did same thing when I implemented for my previous employer.
Regards
Anil Patel
On Jun 9, 2008, at 3:02 PM, Adrian Crum wrote:
> David E Jones wrote:
>> I can think of two main ways of doing this:
>> 1. list explicitly/inline the roles you want to show (instead of
>> doing a query)
>> 2. create a parent role and put the roles you want under it and
>> query by the parent ID
>
> I like idea #2. Using that approach, a user could expand the list
> just by adding child roles.
>
>> As for which roles to use, and whether to create or not, it's
>> totally okay to add new roles but you might consider keeping the
>> roles used more general and use ideas like "manager" and
>> "worker" (or assignee, performer, whatever) instead of very
>> specific ones.
>
> I was planning on keeping it as generic as possible.
>
> Thank you for the advice!
>
> -Adrian
>
>
>> On Jun 9, 2008, at 11:45 AM, Adrian Crum wrote:
>>> I have expanded the functionality of Asset Maintenance. Currently,
>>> maintenance tasks are assigned automatically to the logged-in user
>>> and there is no way to change it or assign the task to someone
>>> else. I have added the ability to assign maintenance tasks to
>>> someone else.
>>>
>>> The assignment requires a party role. Presenting the user with a
>>> list of all roles to pick from is not user-friendly because the
>>> list is quite long. I would like to have a smaller list that is
>>> more Fixed Asset Maintenance specific. I'm not sure how I should
>>> implement the smaller role list.
>>>
>>> I'm thinking the list should contain three roles: an outside
>>> service, a maintenance manager, and a maintenance worker. Should I
>>> use existing roles, or create new ones?
>>>
>>> Another idea is to populate the list with parties/roles that are
>>> already related to the fixed asset in question.
>>>
>>> Any advice would be appreciated!
>>>
>>> -Adrian
Re: Question About The Asset Maintenance Component
Posted by Adrian Crum <ad...@hlmksw.com>.
David E Jones wrote:
>
> I can think of two main ways of doing this:
>
> 1. list explicitly/inline the roles you want to show (instead of doing a
> query)
> 2. create a parent role and put the roles you want under it and query by
> the parent ID
I like idea #2. Using that approach, a user could expand the list just
by adding child roles.
> As for which roles to use, and whether to create or not, it's totally
> okay to add new roles but you might consider keeping the roles used more
> general and use ideas like "manager" and "worker" (or assignee,
> performer, whatever) instead of very specific ones.
I was planning on keeping it as generic as possible.
Thank you for the advice!
-Adrian
> On Jun 9, 2008, at 11:45 AM, Adrian Crum wrote:
>
>> I have expanded the functionality of Asset Maintenance. Currently,
>> maintenance tasks are assigned automatically to the logged-in user and
>> there is no way to change it or assign the task to someone else. I
>> have added the ability to assign maintenance tasks to someone else.
>>
>> The assignment requires a party role. Presenting the user with a list
>> of all roles to pick from is not user-friendly because the list is
>> quite long. I would like to have a smaller list that is more Fixed
>> Asset Maintenance specific. I'm not sure how I should implement the
>> smaller role list.
>>
>> I'm thinking the list should contain three roles: an outside service,
>> a maintenance manager, and a maintenance worker. Should I use existing
>> roles, or create new ones?
>>
>> Another idea is to populate the list with parties/roles that are
>> already related to the fixed asset in question.
>>
>> Any advice would be appreciated!
>>
>> -Adrian
>
>
Re: Question About The Asset Maintenance Component
Posted by David E Jones <jo...@hotwaxmedia.com>.
I can think of two main ways of doing this:
1. list explicitly/inline the roles you want to show (instead of doing
a query)
2. create a parent role and put the roles you want under it and query
by the parent ID
As for which roles to use, and whether to create or not, it's totally
okay to add new roles but you might consider keeping the roles used
more general and use ideas like "manager" and "worker" (or assignee,
performer, whatever) instead of very specific ones.
-David
On Jun 9, 2008, at 11:45 AM, Adrian Crum wrote:
> I have expanded the functionality of Asset Maintenance. Currently,
> maintenance tasks are assigned automatically to the logged-in user
> and there is no way to change it or assign the task to someone else.
> I have added the ability to assign maintenance tasks to someone else.
>
> The assignment requires a party role. Presenting the user with a
> list of all roles to pick from is not user-friendly because the list
> is quite long. I would like to have a smaller list that is more
> Fixed Asset Maintenance specific. I'm not sure how I should
> implement the smaller role list.
>
> I'm thinking the list should contain three roles: an outside
> service, a maintenance manager, and a maintenance worker. Should I
> use existing roles, or create new ones?
>
> Another idea is to populate the list with parties/roles that are
> already related to the fixed asset in question.
>
> Any advice would be appreciated!
>
> -Adrian