New vendor, new paperwork. Tell your app what changed.
A delivery arrives at a warehouse. Someone checks the boxes, picks up the paper delivery slip and records what came in.
The business wants an application to help with that work: read the delivery information, identify the vendor, list the items and quantities, and make the receiving record available to the team.
The customer can describe that job perfectly well. They do it every day.
Then a new vendor starts shipping.
Their delivery slip looks different. They call the product code an item reference. They put quantities in a different place. And they include something the business now wants to keep: a lot number for each item.
The customer's request is simple: “This vendor includes a lot number. Capture that too.”
Start with the business request
That sentence tells us something useful about how software can work. The person using the application already understands the new requirement. They need a way to express it that the application can use.
With IntentSharp, developers can build .NET applications that load their instructions and the definition of the information they need at run time. Those definitions can live outside a compiled C# class.
AI can help turn the customer's request into an updated definition. The application then uses that definition to collect and check the additional information.
For our delivery example, the original request might be:
“Read this delivery slip. Record the vendor, delivery date, item reference and quantity received for each item.”
The updated request adds:
“Also record each item's lot number when the slip includes one. Keep the lot number as text, including any leading zeros.”
That last detail comes straight from the business. A lot number such as 004821 is an identifier, so keeping the leading zeros matters.
What an intent describes
An intent describes the job the application wants done. Alongside the instructions, a definition can describe the information the application expects back: the names of the fields, their types and the checks that apply.
In ordinary language, this is the application's working agreement about a delivery record. It knows that an item has a reference, that its quantity is a number and that its lot number is text.
When the requirement changes, AI can help express both sides of the change: what to look for and how to represent it. The updated intent can include the instruction to capture lot numbers and the additional field in the data model.
IntentSharp supports definitions supplied at run time and catalogs that load intent files. A developer can use those capabilities to build a customer-facing setup experience: describe the change, see the proposed definition, try it on a delivery slip and save the version the application will use.
The setup experience belongs to the application. IntentSharp provides the .NET capabilities that let it work with those definitions.
From a request to a receiving record
Here is how that experience could look in a receiving application:
- The customer describes the change. “Our new vendor includes lot numbers. We need to keep them with the items we receive.”
- AI helps update the intent. The definition gains a lot-number field and instructions for capturing it, including what to return when a slip has no lot number.
- The application shows the result. A sample slip becomes a receiving record the customer can inspect: vendor, date, item, quantity and lot number.
- The selected definition becomes reusable. The receiving workflow loads it for the relevant vendor or customer and uses it on later deliveries.
The document can enter the workflow through the application's document-reading or OCR step. IntentSharp works with the input the application supplies. That gives developers room to choose how paper, scans and digital documents reach the same receiving workflow.
Different vendors can have different definitions while sharing the same calling code. One vendor's slip may include a lot number; another may include a serial number or storage instruction. The application can select the definition that fits the work.
Let the application use the change
The useful part goes beyond reading another field.
A developer can build a review screen that reads the definition and shows the right fields. A flexible record store can keep the additional information. An export can map the selected fields to the system that receives them.
In an application built that way, adding a lot number can become a definition update rather than a new C# model for every vendor. The developer designs the screens, storage and integrations to use changing definitions, and the customer gets a practical way to tell the application what changed.
IntentSharp also gives developers ways to check the returned information. Catalog definitions can check supported field requirements and types, while application validators can apply business checks such as matching an item reference to the product catalog. Developers choose the checks and retry limits that fit their workflow.
The result is a closer connection between a business requirement and the software that carries it out. The customer describes the information they need. AI helps express that requirement. The application uses the updated intent and data definition.
Make room for the next change
Delivery slips are one example. The same approach can apply to inspection sheets, service reports, equipment records and other documents whose details vary between customers and suppliers.
For each one, start with the person who knows the job. What do they need the application to understand? What information do they want to keep? What changed since last time?
Those are questions a business user can answer.
“This vendor includes a lot number. Capture that too.” With a flexible application and IntentSharp, that everyday request can become an updated definition the software puts to work.