Smart Vendor and Procurement System Details – Click Here
Explore the Smart Vendor and Procurement System through a detailed walkthrough of its application interface and the visual logic behind its workflows. This training brings together the user experience and redSling Logic Builder configuration to show how pages, forms, component events, variables, validation, and backend requests work together across the application.
Begin by accessing the application and signing in with the available user credentials. After authentication, explore the main navigation and the connected areas for vendor management, procurement, purchase orders, asset management, invoices, and incident reporting. The walkthrough introduces how these functions are organized within a centralized application before examining the logic that supports them.
The Vendor Management section demonstrates how users can review existing vendors in a structured table and open the form for adding a new vendor. Explore fields for vendor name, contact information, address, category, and supporting details. Dropdown controls provide predefined selections, helping users enter information that follows the application’s configured options.
The walkthrough then moves into the project workspace and opens the VendorUpdated page. Review its search controls, filtering options, Add Vendor action, and vendor table before switching to Logic Builder. See how component events connect form inputs and selections to variables, making the entered information available for conditions, JSON processing, and API-related operations.
Next, explore the purchase-request workflow in the Procurement Center. The interface organizes request information, required items, quantities, category, delivery requirements, and supporting details into sections. Users can complete the form and submit their request through the primary action.
In Logic Builder, review how the Procurement Center prepares the information needed for backend processing. The flow parses stored login information, retrieves user-related values, and builds key-value structures containing requester details, the related vendor, subtotal, tax, total, justification, approval status, and purchase-request number.
The procurement logic also demonstrates how API requests use the configured backend base URL, POST operations, JSON content, and authorization information. Review how the response is processed, including retrieving an inserted ID and iterating through returned data where required. This connects the information entered in the interface to the records processed by the backend.
Continue into the Purchase Order Center to review the interface for approved purchase requests and generated purchase orders. Open the Generate Purchase Order form, review vendor information, and enter order-related details such as dates and references. The purchase-order table provides a central place to review available orders and access their associated actions.
The Purchase Order logic walkthrough shows how visual blocks prepare purchase-request and purchase-order information for backend processing. Explore API configuration with authorization headers and JSON payloads, along with response handling that allows generated order information to be reflected in the application.
The application walkthrough also introduces Asset and GRN Management, where users can review asset and goods receipt information in a structured table. Explore the available records, their associated details, and the actions provided for individual entries.
The developer walkthrough then examines the Asset_ManageQR page. Review asset information such as asset code, name, category, description, manufacturer, warranty details, purchase price, vendor, department, and status. Open the Add Asset workflow and see how its inputs and selections connect to variables through component events.
In the asset logic, follow how the captured values are assembled into a key-value structure and sent through the configured API workflow. Review how the response is stored and used to display confirmation when an asset has been successfully created and assigned. The walkthrough also identifies the response handling represented for unsuccessful operations.
Next, explore the vendor invoice workflow and its connection to the Finance Center. The interface allows users to select the appropriate vendor and enter invoice details, dates, amounts, and supporting information before submission.
Within Finance Center Logic Builder, review how the flow retrieves login information and extracts the user ID. Follow the purchase-order selection process, iteration through returned purchase-order data, and extraction of values such as purchase-order ID and name. The logic prepares a POST request using the backend base URL, authorization token, and filter information to retrieve relevant records.
The walkthrough then covers incident reporting and maintenance. Open the Report New Incident form and review fields for the asset, category, priority, location, and detailed description. The interface also includes resolution-related information and actions for cancelling or submitting the incident.
In the Incident and Maintenance page, explore the incident search, listing table, and Report Incident action. Review how component events capture information from inputs and selections, including department and maintenance assignment, and pass those values into the underlying workflow.
The final major section focuses on User Profile. Review the personal information fields for first name, last name, email, phone number, department, role, and bio, together with Edit functionality and quick links such as Change Password and Notifications.
The profile logic retrieves login information from Local Storage and the user token from Session Storage. It parses the stored JSON and extracts properties such as email, role, department, phone number, bio, first name, last name, full name, and user ID into variables. These values populate the corresponding profile components, while component events capture changes made by the user.
The tutorial also explains the password-confirmation check. When a new password and confirmation password do not match, the flow displays a warning and clears the confirmation field so the user can enter it again.
For profile submission, review the PUT API request configured with the user URL, JSON content type, authorization token, and updated profile information. The payload includes values such as phone number, bio, password information, and the last-modified date. A successful response triggers a confirmation that the user details were updated.
The walkthrough concludes by opening the application in Preview mode and reviewing the Login screen with its email field, password field, and Login action. Together, both walkthroughs show how the application’s user-facing screens connect to visual logic for data capture, validation, authenticated requests, response handling, and user feedback.
What you’ll learn