Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add new FAQ #2159

Merged
merged 3 commits into from
Jan 3, 2025
Merged

Add new FAQ #2159

merged 3 commits into from
Jan 3, 2025

Conversation

usama9500
Copy link
Collaborator

@usama9500 usama9500 commented Nov 26, 2024

  • Added new FAQs from general and help channel from discord

Summary by CodeRabbit

  • New Features

    • Added several new FAQs addressing retrieving lane/group information, modifying process instances, and mapping input/output for subprocesses.
  • Enhancements

    • Expanded existing FAQ answers with detailed guidance and practical examples, particularly for the approval process and external system integration.
  • Clarifications

    • Included specific instructions for service task configuration, error handling, and communication in SpiffArena behind a proxy.
  • Code Examples

    • Added code snippets to illustrate configurations and usage throughout the FAQ.

@usama9500 usama9500 requested a review from burnettk November 26, 2024 08:51
Copy link
Contributor

coderabbitai bot commented Nov 26, 2024

📝 Walkthrough

Walkthrough

The changes in the docs/Support/FAQ.md file involve the addition of new questions and answers, as well as modifications to existing entries. New FAQs cover topics such as retrieving lane or group information during task execution and modifying process instances during execution. Additionally, existing entries have been expanded with detailed explanations, clarifications, and code examples to enhance user understanding of SpiffWorkflow and SpiffArena functionalities.

Changes

File Change Summary
docs/Support/FAQ.md - Added new FAQs: "Retrieve Lane or Group Information," "Modify Process Instances during Execution."
- Updated existing FAQs with expanded answers and examples, including details on the approval process, integration features, configuration, and error handling.
- Included code snippets for service tasks and authentication management.

Possibly related PRs

  • docker_permission_issue_faq #2083: Updates the FAQ section on "Fixing Resolving Docker Permission Issues When Installing SpiffArena (Linux)," which is also addressed in this PR, indicating a direct connection in content updates related to Docker permissions.

Suggested reviewers

  • burnettk

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (4)
docs/Support/FAQ.md (4)

Line range hint 1-592: Consider reorganizing FAQs into topic-based sections

The FAQs would be more navigable if organized into topic-based sections such as:

  • Getting Started
  • Installation & Configuration
  • Authentication & Security
  • Integration & External Systems
  • Workflow Design
  • Task Management
  • Troubleshooting
🧰 Tools
🪛 Markdownlint (0.35.0)

543-543: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


544-544: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


583-591: Add language identifier to code block

Add the Python language identifier to the code block for better syntax highlighting:

-  ```
+  ```python
   import uuid
   unique_id = str(uuid.uuid4())

---

`468-470`: **Remove line number artifacts**

Remove the line numbers ("468~", "469~", "470~") that appear to be artifacts in the text.

---

`543-544`: **Fix list indentation**

Adjust the indentation of the unordered list items to be consistent with the rest of the document:

```diff
-  - Use single `=` for variable assignments (e.g., `result = "approve"`).
-  - Avoid using double `==`, as it is a comparison operator, not an assignment.
+ - Use single `=` for variable assignments (e.g., `result = "approve"`).
+ - Avoid using double `==`, as it is a comparison operator, not an assignment.
🧰 Tools
🪛 Markdownlint (0.35.0)

543-543: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


544-544: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4c01492 and 174e77e.

📒 Files selected for processing (1)
  • docs/Support/FAQ.md (4 hunks)
🧰 Additional context used
🪛 Markdownlint (0.35.0)
docs/Support/FAQ.md

543-543: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


544-544: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

docs/Support/FAQ.md Outdated Show resolved Hide resolved
docs/Support/FAQ.md Outdated Show resolved Hide resolved
docs/Support/FAQ.md Outdated Show resolved Hide resolved
docs/Support/FAQ.md Outdated Show resolved Hide resolved
Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (4)
docs/Support/FAQ.md (4)

491-493: Enhance service task explanation.

The explanation about service tasks could be more detailed. Consider adding:

  • A note about error handling
  • Common troubleshooting steps
  • Links to relevant documentation

544-548: Add error handling to group members example.

The code example for retrieving group members should include error handling:

-  group_members = get_group_members(lane_name)
+  try:
+      group_members = get_group_members(lane_name)
+  except Exception as e:
+      logging.error(f"Failed to retrieve group members for lane {lane_name}: {e}")
+      raise

535-536: Fix list indentation.

The unordered list items have inconsistent indentation. According to Markdown best practices, list items should have consistent indentation.

-  - Use single `=` for variable assignments (e.g., `result = "approve"`).
-  - Avoid using double `==`, as it is a comparison operator, not an assignment.
+ - Use single `=` for variable assignments (e.g., `result = "approve"`).
+ - Avoid using double `==`, as it is a comparison operator, not an assignment.
🧰 Tools
🪛 Markdownlint (0.37.0)

535-535: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


536-536: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


516-516: Fix grammar: Add missing article.

Add the missing article "the" before "SpiffWorkflow":

-In SpiffWorkflow library,
+In the SpiffWorkflow library,
🧰 Tools
🪛 LanguageTool

[uncategorized] ~516-~516: Possible missing article found.
Context: ...flow library vs. SpiffArena? A: In SpiffWorkflow library, service tasks do not have buil...

(AI_HYDRA_LEO_MISSING_THE)

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 174e77e and a74e64e.

📒 Files selected for processing (1)
  • docs/Support/FAQ.md (3 hunks)
🧰 Additional context used
🪛 LanguageTool
docs/Support/FAQ.md

[uncategorized] ~516-~516: Possible missing article found.
Context: ...flow library vs. SpiffArena? A: In SpiffWorkflow library, service tasks do not have buil...

(AI_HYDRA_LEO_MISSING_THE)

🪛 Markdownlint (0.37.0)
docs/Support/FAQ.md

535-535: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


536-536: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

Comment on lines +531 to +553
### **45: Mapping input/Output for Call Activity Subprocess**
**Q:** How do I map input and output for Call Activity subprocesses?**

**A:** In the subprocess:
- Use single `=` for variable assignments (e.g., `result = "approve"`).
- Avoid using double `==`, as it is a comparison operator, not an assignment.

Also, ensure input/output mappings are correctly defined in the parent process to facilitate data transfer.

### **47: Retrieve Lane or Group Information**
**Q:** How do I retrieve lane or group information during task execution?**

**A:**
Users need to retrieve the group or username associated with a specific lane during task execution for sending notifications or dynamic task assignment.
- Use the lane name with `get_group_members()` to fetch the corresponding group or users dynamically:
```python
group_members = get_group_members(lane_name)
```
- Refer to the [Pools and Lanes Documentation](https://spiff-arena.readthedocs.io/en/latest/Building_Diagrams/pools_and_lanes.html) and [Script Tasks Documentation](https://spiff-arena.readthedocs.io/en/latest/Building_Diagrams/Script_Tasks.html) for additional details.

### **48: Modify Process Instances during Execution**
**Q:** Can I modify process instances during execution?**

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🛠️ Refactor suggestion

Fix FAQ numbering sequence.

The FAQ numbering sequence is broken:

Please renumber the FAQs sequentially to maintain consistency.

🧰 Tools
🪛 Markdownlint (0.37.0)

535-535: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)


536-536: Expected: 0; Actual: 2
Unordered list indentation

(MD007, ul-indent)

@burnettk burnettk merged commit 818fbcb into main Jan 3, 2025
24 checks passed
@burnettk burnettk deleted the update_faq branch January 3, 2025 19:21
@coderabbitai coderabbitai bot mentioned this pull request Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants