You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "BJ Freeman (JIRA)" <ji...@apache.org> on 2010/08/30 17:45:53 UTC

[jira] Commented: (OFBIZ-3913) Automated action triggered by event

    [ https://issues.apache.org/jira/browse/OFBIZ-3913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904227#action_12904227 ] 

BJ Freeman commented on OFBIZ-3913:
-----------------------------------

some thoughts.
there will be times that the admin will want to fix which printers a party (login) uses. so a screen to allow that. maybe linking to the loggin's PartPreference would possibly be a better way.


the ExternalDevice should be updated before accessing the ExternalDeviceUserAction, since network failures can cause printer to be offline.

is the ExternalDevice type to define like a HPlaser, if so then need a externalDevicejobtype for like Invoices, PO. and this needs to be one to many incase they use one printer for many tasks. t

also need the info about how many pages are printed so a restart will pick up on the last page and continue.

leave a hook for automatically switching printers if two of the same type Job type are defined, and the first goes offline.

> Automated action triggered by event
> -----------------------------------
>
>                 Key: OFBIZ-3913
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-3913
>             Project: OFBiz
>          Issue Type: Bug
>          Components: framework
>    Affects Versions: SVN trunk
>            Reporter: Nicolas Malin
>         Attachments: ExternalDevice.patch, ExternalDevice.png
>
>
> Following a thread on the dev list, related to a printer automated selection, by an user and an event, here is a first draft.
> I added a new entity, ExternalDevice, which list all devices OFBiz can reach (and the associated command). This entity is related to an ExternalDeviceType and each record has a status, so we know if the device is available, out of order, in maintenance, waiting, etc...
> Then I added another entity, ExternalDeviceUserAction, which defines a device for an user, and/or an action through Enumeration. Finally, I added a service which find the commnand to execute based on an action and/or an user.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.