> For the complete documentation index, see [llms.txt](https://help.smallbuilder.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.smallbuilder.com/ko/smallbuilder-schedules/undefined-1/schedule-configurator.md).
# Schedule Configurator 사용하는 방법
Opportunity - Opportunity Product - LineItemSchedule을 사용한 Schedule Configurator 사용법
1. Start Here 페이지를 참고하여 Sample Data를 생성해 줍니다.
2. Line-Item Object의 Name Field를 Product의 Name을 가지는 포뮬러 함수 필드로 변경 해줍니다.
3. Add Button을 사용하여 원하는 페이지 레이아웃에 Schedule Configurator 사용을 위한 Quick Action을 추가해 줍니다.
4. Parent Object의 record Detail 페이지에 추가한 'Schedule' 버튼을 클릭하여 Schedule Configurator를 사용합니다.
5. CreateAll 버튼을 눌러 모든 라인 아이템의 일정을 생성합니다.
6. Create 버튼을 눌러 왼쪽 Tab에 활성화된 LineItem에 대한 일정을 생성합니다.
7. ScheduleDate를 기준으로 일정 정렬이 가능합니다.
8. 범위를 넘어서는 값을 입력할 시 붉은색 표기를 통해 유효하지 않은 값임을 사용자에게 알립니다.
9. '+'버튼과 휴지통 버튼을 사용하여 일정을 추가 삭제할 수 있습니다.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.smallbuilder.com/ko/smallbuilder-schedules/undefined-1/schedule-configurator.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
