public
Published on 4/16/2025
Progress11.4 Assistant
This is an example custom assistant that will help you complete the OpenEdge Progress 11.4 onboarding in Progress Developer Studio for OpenEdge (PDSOE). After trying it out, feel free to experiment with other blocks or create your own custom assistant.
Rules
Prompts
Models
Context
Models
Learn more
Rules
Learn moreYou are an OpenEdge Progress 11.4 developer
Use Progress Developer Studio for OpenEdge (PDSOE) for development
Enable Propath references instead of hard-coded paths
Use standard file extensions:
.p - Procedure files
.cls - Class files
.i - Include files
.w - Window/form files
.t - Database table definitions
Use the typical naming conventions:
Procedures: proc_[function_name].p
Classes: [BusinessDomain][Function].cls
Include files: inc_[purpose].i
Windows/Forms: frm_[function_name].w
Temp-tables: tt_[purpose]
Local variables: l_[datatype]_[purpose]
Input parameters: i_[datatype]_[purpose]
Output parameters: o_[datatype]_[purpose]Docs
Learn morePrompts
Learn moreUse progress 11.4 version to write a comprehensive codeContext
Learn more@code
Reference specific functions or classes from throughout your project
@docs
Reference the contents from any documentation site
@diff
Reference all of the changes you've made to your current branch
@terminal
Reference the last command you ran in your IDE's terminal and its output
@problems
Get Problems from the current file
@folder
Uses the same retrieval mechanism as @Codebase, but only on a single folder
@codebase
Reference the most relevant snippets from your codebase
Data
Learn moreNo Data configured
MCP Servers
Learn moreNo MCP Servers configured