laatzen/LaaProductionWeb
2024-06-26 08:05:20 +02:00
..
Data Label print: box & test labelsas api calls 2024-06-26 08:05:20 +02:00
LaaProduction.Console Label print: box & test labelsas api calls 2024-06-26 08:05:20 +02:00
LaaProduction.Data.SQL TempCalibration: auf mehrere flanschen 2024-04-22 16:31:22 +02:00
LaaProduction.Http OMNI+ plugin system, ready for testing on the test benches 2024-05-30 16:34:32 +02:00
LaaProduction.Personalization WEB API: Cordonel Requirements endpoint 2024-04-15 11:17:19 +02:00
LaaProduction.Search Cordonel EOL API 2024-03-06 12:48:08 +01:00
LaaProduction.Services WEB API: Cordonel Requirements endpoint 2024-04-15 11:17:19 +02:00
LaaProduction.SharedModels gtb: pwd change, register 2024-02-20 12:17:07 +01:00
LaaProduction.SQL API cordonel requirements 2024-04-30 16:28:03 +02:00
LaaProductionVFM Label print: box & test labelsas api calls 2024-06-26 08:05:20 +02:00
LaaProductionWeb Omni inspection ui & remote control 2024-06-17 16:48:56 +02:00
PendingEmails WEB API: Cordonel Requirements endpoint 2024-04-15 11:17:19 +02:00
RoutesBuilder Production web latest 2024-05-07 15:49:51 +02:00
LaaProductionWeb.sln Label print: box & test labelsas api calls 2024-06-26 08:05:20 +02:00
README.md Update README.md 2024-03-22 10:42:09 +00:00

LaaProductionWeb

1. Wildcard search - find API explanation and usage hier otherwise you can use it as web UI hier.

  • The wildcard search UI works with the implemented API explained above, also requires WEB_API_Explorer user role. Once you have access to the web page the usage is as simple as posible. You can select or not a fields that you whant to see in response to the search. By default are all listed fields returned.
    ... then type your search string, the search is processed against serial numbers, pcb id, eregister or genesis meter addresses. So you can type a hole number or part of it. Depending on the input you can becomm one or more results. For instance below was typed last part of customer specific serial number. ...

2. Cordonel EOL API

Note: Each of the following endpoints returns the actual state of the EOL progress model. The errors from the API are also written to the http response content in the form from IDictionary<string, string>.

  • DELETE: /api/Cordonels/EOLProgress - saves the current progress in backup table and resets the values of the existing one except the PcbId and AddHost.
  • GET: /api/Cordonels/EOLProgress - gets existing progress model by its PcbId or creates a new one if not exists.
  • POST: /api/Cordonels/EOLProgress - sets the completition status of the current progress by its PcbId, there are no more changes accepted afterwards, the only possible way is to delete the progress for the PcbId.
  • PUT: /api/Cordonels/EOLProgress - changes progress steps in case they are not already changed.
  • Test the API hier - request parameters and models are described there
    // The Status type is a one of the following strings: null, FAIL, NA, OK - other values are ignored!
    // Client can interpret the Status as string or enum, but the API accepts only strings.
    public class EOLProgressModel
    {
        public int Id { get; set; }

        public int PcbId { get; set; }

        public DateTime? AddDate { get; set; }

        public int? RequirementId { get; set; }

        public Status RequirementChecked { get; set; }

        public Status PasswordFileInstalled { get; set; }

        public Status ProductionStatusChecked { get; set; }

        public Status ParameterizationDone { get; set; }

        public Status RebootDone { get; set; }

        public Status StoreConfigurationDone { get; set; }

        public Status ExportDone { get; set; }

        public long? RaioCheckId { get; set; }

        public DateTime? SentinelDate { get; set; }

        public Status Completed { get; set; }

        public DateTime? CompleteDate { get; set; }

        public string EditedBy { get; set; }
    }