FLEXSCHE CarryOut 4

iOS Universel / Productivité

FLEXSCHE CarryOut supports the execution of plans created in the production scheduler.

Manufacturing plans created in the production scheduler will maximize their value only if they are executed properly on the manufacturing site based on the plan. However, it is not always possible for operations in the manufacturing site to proceed according to plan.

FLEXSCHE CarryOut's mission is to support the high-level realization of a simple plan operation cycle, which involves real-time monitoring of work and progress, collecting actual results, and reflecting the results in the plan by feeding the information back into the scheduler.

This application functions as the front-end of FLEXSCHE CarryOut on the manufacturing site.

The plan data created in the production scheduler is exported to the server, and the plan can be viewed in real-time using the app installed on a mobile device by accessing the server. Work is performed according to the obtained plan, and progress is entered and sent to the server. Each device can share progress on each other's work and check for any delays in the work process in real-time.

# System Requirements
In addition to this application, you will need the following:

1. FLEXSCHE CarryOut server (version 5)
2. FLEXSCHE GP

# Notice
This application retrieves schedule data via network communication. The device running the application must be able to access the FLEXSCHE CarryOut Server.

# Setting Information
## Hostname
On the login page, you can specify the location of the FLEXSCHE CarryOut Server by entering the URL, such as office.flexsche.com, or the IP address, such as 127.0.0.1.

## Port
You can specify the port number of the FLEXSCHE CarryOut Server. The default port number is 6712.

About Permissions
Full Internet Access is required to retrieve data from FLEXSCHE CarryOut server.

Note
If you have any questions regarding settings or features, please contact us by email. Please note that we cannot respond to inquiries in the review section.

Quoi de neuf dans la dernière version ?

## New Features

- Updated the default footer on the Operation Details screen to display a button that allows actual results to be recorded sequentially for each part.
- Added SendEventOperationByStepDirective. This directive can be used to record operation results for starting the next step, or for interrupting, resuming, or completing the current step.
- Enabled navigation from the header of the Resource Operation List and Resource Chart screens to the Resource List and Resource Details screens.
- Added a setting to hide the navigation buttons on the Resource Chart screen.
- Implemented CoInputComponent, adding support for displaying numeric input fields with thousands separators.

## Bug Fixes

- Fixed an issue where, when an input/output operation was a cluster operation, both the cluster operation and some of its member operations were incorrectly listed in the input/output links.
- Fixed an issue where initial values set in **CheckDirective** were not reflected in properties such as `allChecked$` in CheckGroupComponent.
- Fixed an issue where changes made to operation result properties on the server were not propagated to clients.
- Fixed an issue where using `*coFetchRecordsOnce` more than once simultaneously with the same table name could result in only the first instance retrieving records.
- Fixed an issue where `*coFetchRecordsOnce` did not correctly retrieve records after the first attempt when used with a custom dataset that has no key.
- Fixed an issue where colors assigned to free calendars created from the client side were sometimes not applied correctly.