check call-out 3.1 Buttons, Links and Icons: Button, OnClick Other Event Visible Enabled Vs Navigate To Validation Dependencies Link, Icon Disabled Label <Button <Specify <Specify the <Specify <Specify if <Specify the <Specify the <Mention if there label the operation that default button is link where validation are any name> operation would be visibility enabled or the page will rules on dependencies on that would performed on of the disabled be operation of other form be other events> button> and the if the button> elements and/ or performed condition, if any> buttons> on an any> event> Example: Verify if OnMouseHover Yes, Disabled, by User Verify if Disable the New Submit user name display the always default. Dashboard Username is a user functionality and following Enabled, page valid sunet ID on subsequent password message: after first and user pages if user logs in are correct. provide key entered name and through this “Please If yes, log your in either password button. the user username or match with into the details to sign password registry data. system. in> field. System Configurations <Provide an overview of all the steps or the set ups required to configure an application/program. Also state the intent or purpose behind each set up or configuration. Discuss the possible alternatives, customizations, workaround’s, and dependencies in a particular configuration. In case of Oracle applications, please list all applicable BR100’s or Application set up documents>
check call-out 3.1 Buttons, Links and Icons: Button, Link, Icon Label OnClick Other Event Visible Enabled Vs Disabled Navigate To Validation Dependencies <Button label name> <Specify the operation that would be performed on an event> <Specify the operation that would be performed on other events> <Specify default visibility of the button> <Specify if button is enabled or disabled and the condition, if any> <Specify the link where the page will be if any> <Specify the validation rules on operation of the button> <Mention if there are any dependencies on other form elements and/ or buttons> Example: Submit Verify if user name and password are correct. If yes, log the user into the system. OnMouseHover display the following message: “Please provide your details to sign in> Yes, always Disabled, by default. Enabled, after first key entered in either username or password field. User Dashboard page Verify if Username is a valid sunet ID and user name and password match with registry data. Disable the New user functionality on subsequent pages if user logs in through this button. System Configurations <Provide an overview of all the steps or the set ups required to configure an application/program. Also state the intent or purpose behind each set up or configuration. Discuss the possible alternatives, customizations, workaround’s, and dependencies in a particular configuration. In case of Oracle applications, please list all applicable BR100’s or Application set up documents>
AS%20Functional%20Specification%20Document%20Template_0.docx