Let business users distribute files themselves
A file distribution job prepared in advance by an engineer can be run by the business owner directly from INNORIX Portal. The target devices, the permitted paths and the right to run are all held in Studio, and the business user reviews the files and the conditions for the run, starts the transfer and follows the progress and the result on each device. They need to know nothing about how to reach a server or how to write a transfer script.
- Prepare the distribution job in Studio
- Pick the distribution item in Portal
- Review the permitted files, targets and run conditions
- Start the distribution
- Follow the progress and the per-device result
What this shows is a business user running a device-to-device 1:N distribution job composed by an engineer, directly from Portal. Portal is not a service for handing download links to general end users or for uploading arbitrary files through a browser. Attaching a local file to Portal, or downloading a file from a target server, is not presented here as default behaviour either. File selection in Portal is limited to files on the devices and paths Studio has permitted.
How it is built
- An engineer prepares the devices and paths to distribute to.
In Studio Devices, connect the source server and the receiving target devices, and confirm the paths files can be read from and saved to.
- Compose the distribution Flow in Studio.
In Flows, set the source device and its permitted file path, and the several target devices and their storage paths. Separate what the business owner may change from what stays fixed.
- Attach the job to the business-facing Portal.
Expose that distribution Flow in the Portal configuration and set the right to run per user together with any approval step and execution time window. Confirm the settings your product version actually offers.
- The business owner starts the distribution in Portal.
They pick a permitted distribution job and, where offered, choose the files to distribute from the provided list or confirm the approved targets and time before running it.
- Check the progress and the result.
In Portal, review the overall state of a distribution in progress and the result per target. If they pick the same job while it is already running, point them to the monitoring screen for the existing job rather than starting a duplicate.
Where it is used
- Head office operations distributing notices to branches
Once an engineer has connected the head office document server to the branch servers, an operations owner picks approved material in Portal and distributes it to several branches.
- Delivering price and product information per store
A product operations owner distributes price lists and product data files to the store servers at a set time and checks the transfer result for each store. Whether the store system itself has taken the data in is confirmed separately.
- Delivering work instructions per factory
A quality or production owner distributes approved work instruction files to the factory servers and sees which factories the files reached.
- Distributing marketing material per region
A marketing owner delivers campaign content to the regional servers named in advance. The files delivered and the receiving paths stay within what Studio permits.
- Getting design changes out to the sites
A design owner distributes new drawings and change notices to the site servers and sees which receiving devices were missed. A completed file transfer is kept distinct from site approval and application.
- Delivering an update that needs a time window
An owner starts the job in Portal within the window distribution is allowed in, and where approval is required the transfer follows the approval. The actual approval and time controls are applied to match the product settings.
- Several departments on one distribution environment
Engineers run the shared transfer infrastructure while each department runs, from Portal, only the distribution jobs permitted to it.
Usage guides
Frequently asked questions
Is there a way for business staff to distribute files to several servers without IT?
INNORIX Portal is the interface where a permitted business user runs and monitors, themselves, the device-to-device file transfer jobs an engineer composed in Studio beforehand. They can carry out the distribution work permitted to them with no server access and no script handling.
Can a business user change the target servers or the storage paths freely?
As standard it is designed to run within the devices, paths and permissions defined in Studio. Whether target or file selection is offered at all is decided by the settings of that Portal job and by what the product actually supports. It is not treated as a general file browser with access to arbitrary servers.
Can the same file be distributed to several branches or factories at once?
Yes. Prepare a 1:N distribution Flow in Studio and a business user can run that job from Portal and see the result on each receiving device. How many run concurrently in practice, and the transfer performance, depend on the network and the devices.
Can I attach a file from my PC in Portal and upload it to a server?
The standard Portal in this guide is for running device-to-device transfer jobs. Attaching a file from a user PC directly in the browser, or downloading one, is not part of the standard scope. Web upload and download belongs to INNORIX EX, a separate product, and any bespoke capability needed in Portal has to be reviewed case by case.
Can a distribution require administrator approval, or run only at certain times?
Depending on the work, an operating setup that includes an approval step and an execution time window can be considered. Which approval methods and time controls are actually supported has to be confirmed on the Portal and Studio version you run before applying them.
Can a business owner see the progress of a distribution and the devices that failed?
Portal is designed for a business user to follow the progress and the result of a transfer they ran. Which per-target progress and failure information can be shown, and in what detail, depends on the job type and the product screen; a deeper operational investigation is done in Studio Runs.
What happens if two people start the same distribution job at once?
Where the same job is already running, we recommend a UX that reports the job in progress and moves the user to its monitoring screen, rather than unconditionally creating a duplicate. What counts as a duplicate, and whether it is allowed, has to be confirmed against the execution policy of the product itself.
What is the difference between Portal and Studio?
Studio is the console where an engineer composes and operates Devices, Datasets, Flows and Runs. Portal is the screen where a business owner easily runs the distribution, collection and server-to-server transfer jobs permitted in advance, and sees the result. A Portal user does not compose every device or Flow freely.