In the Guidewire Page Configuration Framework (PCF), navigating between different locations is handled via specialized generated methods. While Pages and Popups use methods like go() or push(), Worksheets (which appear in the workspace at the bottom of the screen) use a unique naming convention.
1. Navigating to Worksheets
When a developer creates a Worksheet PCF (suffix .ws), Guidewire Studio automatically generates a static method to launch that worksheet. According to the InsuranceSuite Developer Fundamentals course, the correct method to open a worksheet is goInWorkspace() (Option D).
When you configure a TextCell or Link within a Row Iterator, the Action property defines what happens when the user clicks the content. By calling ContactWS.goInWorkspace(currentContact), the application server:
Identifies the current row ' s data object (currentContact).
Initializes the ContactWS worksheet.
Pushes the worksheet into the Workspace area (the lower section of the UI), allowing the user to view contact details without losing their place on the main Claim page.
2. Why other options are incorrect
Option A: This looks like a constructor call, which is syntactically valid Gosu but does not trigger the PCF navigation logic required to render the UI.
Option B: actionAvailable is a Boolean property that determines if the click is enabled; it is not the location where the navigation logic itself is written. Furthermore, .push() is typically used for Popups, not Worksheets.
Option C: goInWorksheet is a common misremembering of the syntax. The official Guidewire method name used in the generated PCF classes is specifically goInWorkspace.
This pattern of using Worksheets for " side-bar " or " bottom-bar " details is a key UI/UX best practice in Guidewire to maintain context for the user during complex data entry tasks.
