When we talk about the "full link" in Scriptcase, we are referring to the seamless integration between the Database, the Business Logic, and the User Interface. Here is how the architecture flows:
index.php?app=prod_details&prod_id=prod_id
Scenario: Open an ERP page with current order ID.
Full Link:
https://erp.company.com/order.aspx?id=order_number
Security Note: Use [token] for authentication if required.
The true power of the Full Link lies in passing parameters. Here is how Scriptcase interprets incoming parameters in a Full Link: scriptcase full link
Example Full Link:
server/reports/sales_grid.php?month=April®ion=North
| Problem | Likely Cause | Solution |
|---------|--------------|----------|
| Link shows raw field | Wrong placeholder case | Use exact field name as in DB/scriptcase |
| Filters not preserved | Missing @search | Append &appname_search=@search |
| Infinite redirect loop | Target app redirects back | Add &nm_x=1 to break loop |
| Security error | Missing token/session | Include &app_var_session=1 | When we talk about the "full link" in
Scriptcase is installed on a web server (local or cloud). Once installed, users access it via a browser. The interface is divided into projects. Each project can contain multiple applications (forms, grids, reports).