If AI can't give us multi-user import instead of the single queue then it would be good if the queue can be prioritized so field imports comes before email report/bridge import.
Guest
 |
We protect people and the environment by helping customers safely and efficiently manage the world’s energy infrastructure. |
American Innovations
12211
Technology Blvd. |
Contact UsSales
and Support: |
|
Follow-up:
We will still retain the import log for the Allegro file in path #1.
Attachments Open full size
Initial discussion around this seems to show two opportunities.
1. Similar to how subscriptions import Allegro files directly, apply that methodology to all field imports. This would mean that the Allegro import file is pushed directly into PCS and not queued at all. We expect this to expedite the field imports quite a bit. There may be future files (such as with images) that have to process through the queue, but the vast majority would load right in.
2. Build out a prioritization option in PCS. This requires some more extensive discussion as we would have to consider items that are scheduled (email notifications, scheduled export bridges to other systems, etc) that may not want their priorities changed ad-hoc.
If I have stated these options correctly, then is there a priority for developing one over the other? Thanks!
Attachments Open full size