diff --git a/.dockerignore b/.dockerignore
new file mode 100644
index 00000000000..1cf061121fc
--- /dev/null
+++ b/.dockerignore
@@ -0,0 +1,2 @@
+build/
+.github/
diff --git a/.editorconfig b/.editorconfig
new file mode 100644
index 00000000000..1692977cec8
--- /dev/null
+++ b/.editorconfig
@@ -0,0 +1,18 @@
+# EditorConfig is awesome: https://EditorConfig.org
+
+# Top-most EditorConfig file
+root = true
+
+# Unix-style newlines with a newline ending every file
+[*]
+end_of_line = lf
+insert_final_newline = true
+indent_style = space
+indent_size = 2
+trim_trailing_whitespace = true
+
+[*.rb]
+charset = utf-8
+
+[*.md]
+trim_trailing_whitespace = false
diff --git a/.gitattributes b/.gitattributes
new file mode 100644
index 00000000000..3069c432317
--- /dev/null
+++ b/.gitattributes
@@ -0,0 +1 @@
+source/javascripts/lib/* linguist-vendored
diff --git a/.github/ISSUE_TEMPLATE/bug.md b/.github/ISSUE_TEMPLATE/bug.md
new file mode 100644
index 00000000000..43305a233da
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug.md
@@ -0,0 +1,22 @@
+---
+name: Report a Bug
+about: Create a report to help us improve
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+**Bug Description**
+A clear and concise description of what the bug is and how to reproduce it.
+
+**Screenshots**
+If applicable, add screenshots to help explain your problem.
+
+**Browser (please complete the following information):**
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+**Last upstream Slate commit (run `git log --author="\(Robert Lord\)\|\(Matthew Peveler\)\|\(Mike Ralphson\)" | head -n 1`):**
+Put the commit hash here
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 00000000000..16f4beed616
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+ - name: Questions, Ideas, Discussions
+ url: https://github.com/slatedocs/slate/discussions
+ about: Ask and answer questions, and propose new features.
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
new file mode 100644
index 00000000000..151e45d78cd
--- /dev/null
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -0,0 +1,5 @@
+
\ No newline at end of file
diff --git a/.github/dependabot.yml b/.github/dependabot.yml
new file mode 100644
index 00000000000..d17e8826d4f
--- /dev/null
+++ b/.github/dependabot.yml
@@ -0,0 +1,9 @@
+version: 2
+updates:
+- package-ecosystem: bundler
+ directory: "/"
+ schedule:
+ interval: daily
+ open-pull-requests-limit: 10
+ target-branch: dev
+ versioning-strategy: increase-if-necessary
diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml
new file mode 100644
index 00000000000..f705b7e7af4
--- /dev/null
+++ b/.github/workflows/build.yml
@@ -0,0 +1,42 @@
+name: Build
+
+on:
+ push:
+ branches: [ '*' ]
+ pull_request:
+ branches: [ '*' ]
+
+jobs:
+ test:
+ runs-on: ubuntu-latest
+
+ strategy:
+ matrix:
+ ruby-version: [2.5, 2.6, 2.7, 3.0]
+
+ steps:
+ - uses: actions/checkout@v2
+ - name: Set up Ruby
+ uses: ruby/setup-ruby@v1
+ with:
+ ruby-version: ${{ matrix.ruby-version }}
+
+ - uses: actions/cache@v2
+ with:
+ path: vendor/bundle
+ key: gems-${{ runner.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }}
+ restore-keys: |
+ gems-${{ runner.os }}-${{ matrix.ruby-version }}-
+ gems-${{ runner.os }}-
+
+ # necessary to get ruby 2.3 to work nicely with bundler vendor/bundle cache
+ # can remove once ruby 2.3 is no longer supported
+ - run: gem update --system
+
+ - run: bundle config set deployment 'true'
+ - name: bundle install
+ run: |
+ bundle config path vendor/bundle
+ bundle install --jobs 4 --retry 3
+
+ - run: bundle exec middleman build
diff --git a/.github/workflows/deploy.yml b/.github/workflows/deploy.yml
new file mode 100644
index 00000000000..341cd5f7fbc
--- /dev/null
+++ b/.github/workflows/deploy.yml
@@ -0,0 +1,41 @@
+name: Deploy
+
+on:
+ push:
+ branches: [ 'main' ]
+
+jobs:
+ deploy:
+ runs-on: ubuntu-latest
+ env:
+ ruby-version: 2.5
+
+ steps:
+ - uses: actions/checkout@v2
+ - name: Set up Ruby
+ uses: ruby/setup-ruby@v1
+ with:
+ ruby-version: ${{ env.ruby-version }}
+
+ - uses: actions/cache@v2
+ with:
+ path: vendor/bundle
+ key: gems-${{ runner.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }}
+ restore-keys: |
+ gems-${{ runner.os }}-${{ matrix.ruby-version }}-
+ gems-${{ runner.os }}-
+
+ - run: bundle config set deployment 'true'
+ - name: bundle install
+ run: |
+ bundle config path vendor/bundle
+ bundle install --jobs 4 --retry 3
+
+ - run: bundle exec middleman build
+
+ - name: Deploy
+ uses: peaceiris/actions-gh-pages@v3
+ with:
+ github_token: ${{ secrets.GITHUB_TOKEN }}
+ publish_dir: ./build
+ keep_files: true
diff --git a/.github/workflows/dev_deploy.yml b/.github/workflows/dev_deploy.yml
new file mode 100644
index 00000000000..7f1a40abf5d
--- /dev/null
+++ b/.github/workflows/dev_deploy.yml
@@ -0,0 +1,50 @@
+name: Dev Deploy
+
+on:
+ push:
+ branches: [ 'dev' ]
+
+jobs:
+ deploy:
+ runs-on: ubuntu-latest
+ env:
+ ruby-version: 2.5
+
+ steps:
+ - uses: actions/checkout@v2
+ - name: Set up Ruby
+ uses: ruby/setup-ruby@v1
+ with:
+ ruby-version: ${{ env.ruby-version }}
+
+ - uses: actions/cache@v2
+ with:
+ path: vendor/bundle
+ key: gems-${{ runner.os }}-${{ matrix.ruby-version }}-${{ hashFiles('**/Gemfile.lock') }}
+ restore-keys: |
+ gems-${{ runner.os }}-${{ matrix.ruby-version }}-
+ gems-${{ runner.os }}-
+
+ - run: bundle config set deployment 'true'
+ - name: bundle install
+ run: |
+ bundle config path vendor/bundle
+ bundle install --jobs 4 --retry 3
+
+ - run: bundle exec middleman build
+
+ - name: Push to Docker Hub
+ uses: docker/build-push-action@v1
+ with:
+ username: ${{ secrets.DOCKER_USERNAME }}
+ password: ${{ secrets.DOCKER_ACCESS_KEY }}
+ repository: slatedocs/slate
+ tag_with_ref: true
+
+ - name: Deploy
+ uses: peaceiris/actions-gh-pages@v3.7.0-8
+ with:
+ github_token: ${{ secrets.GITHUB_TOKEN }}
+ destination_dir: dev
+ publish_dir: ./build
+ keep_files: true
diff --git a/.github/workflows/publish.yml b/.github/workflows/publish.yml
new file mode 100644
index 00000000000..d57930a5842
--- /dev/null
+++ b/.github/workflows/publish.yml
@@ -0,0 +1,22 @@
+name: Publish Docker image
+
+on:
+ release:
+ types: [published]
+
+jobs:
+ push_to_registry:
+ name: Push Docker image to Docker Hub
+ runs-on: ubuntu-latest
+ steps:
+ - name: Check out the repo
+ uses: actions/checkout@v2
+
+ - name: Push to Docker Hub
+ uses: docker/build-push-action@v1
+ with:
+ username: ${{ secrets.DOCKER_USERNAME }}
+ password: ${{ secrets.DOCKER_ACCESS_KEY }}
+ repository: slatedocs/slate
+ tag_with_ref: true
+ tags: latest
diff --git a/.gitignore b/.gitignore
index f6fc8c00b25..1d5d08dd245 100644
--- a/.gitignore
+++ b/.gitignore
@@ -14,9 +14,14 @@ tmp
*.DS_STORE
build/
.cache
+.vagrant
+.sass-cache
# YARD artifacts
.yardoc
_yardoc
doc/
-.idea/
\ No newline at end of file
+.idea/
+
+# Vagrant artifacts
+ubuntu-*-console.log
diff --git a/.travis.yml b/.travis.yml
deleted file mode 100644
index 3280d947c9a..00000000000
--- a/.travis.yml
+++ /dev/null
@@ -1,9 +0,0 @@
-sudo: false
-
-language: ruby
-
-rvm:
- - 1.9.3
- - 2.0.0
-
-cache: bundler
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 59ee6a441e5..efee33f7240 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,8 +1,244 @@
# Changelog
+## Version 2.10.0
+
+*April 13, 2021*
+
+* Add support for Ruby 3.0 (thanks @shaun-scale)
+* Add requirement for Git on installing dependencies
+* Bump nokogiri from 1.11.2 to 1.11.3
+* Bump middleman from 4.3.11 to [`d180ca3`](https://github.com/middleman/middleman/commit/d180ca337202873f2601310c74ba2b6b4cf063ec)
+
+## Version 2.9.2
+
+*March 30, 2021*
+
+* __[Security]__ Bump kramdown from 2.3.0 to 2.3.1
+* Bump nokogiri from 1.11.1 to 1.11.2
+
+## Version 2.9.1
+
+*February 27, 2021*
+
+* Fix Slate language tabs not working if localStorage is disabled
+
+## Version 2.9.0
+
+*January 19, 2021*
+
+* __Drop support for Ruby 2.3 and 2.4__
+* __[Security]__ Bump nokogiri from 1.10.10 to 1.11.1
+* __[Security]__ Bump redcarpet from 3.5.0 to 3.5.1
+* Specify slate is not supported on Ruby 3.x
+* Bump rouge from 3.24.0 to 3.26.0
+
+## Version 2.8.0
+
+*October 27, 2020*
+
+* Remove last trailing newline when using the copy code button
+* Rework docker image and make available at slatedocs/slate
+* Improve Dockerfile layout to improve caching (thanks @micvbang)
+* Bump rouge from 3.20 to 3.24
+* Bump nokogiri from 1.10.9 to 1.10.10
+* Bump middleman from 4.3.8 to 4.3.11
+* Bump lunr.js from 2.3.8 to 2.3.9
+
+## Version 2.7.1
+
+*August 13, 2020*
+
+* __[security]__ Bumped middleman from 4.3.7 to 4.3.8
+
+_Note_: Slate uses redcarpet, not kramdown, for rendering markdown to HTML, and so was unaffected by the security vulnerability in middleman.
+If you have changed slate to use kramdown, and with GFM, you may need to install the `kramdown-parser-gfm` gem.
+
+## Version 2.7.0
+
+*June 21, 2020*
+
+* __[security]__ Bumped rack in Gemfile.lock from 2.2.2 to 2.2.3
+* Bumped bundled jQuery from 3.2.1 to 3.5.1
+* Bumped bundled lunr from 0.5.7 to 2.3.8
+* Bumped imagesloaded from 3.1.8 to 4.1.4
+* Bumped rouge from 3.17.0 to 3.20.0
+* Bumped redcarpet from 3.4.0 to 3.5.0
+* Fix color of highlighted code being unreadable when printing page
+* Add clipboard icon for "Copy to Clipboard" functionality to code boxes (see note below)
+* Fix handling of ToC selectors that contain punctutation (thanks @gruis)
+* Fix language bar truncating languages that overflow screen width
+* Strip HTML tags from ToC title before displaying it in title bar in JS (backup to stripping done in Ruby code) (thanks @atic)
+
+To enable the new clipboard icon, you need to add `code_clipboard: true` to the frontmatter of source/index.html.md.
+See [this line](https://github.com/slatedocs/slate/blame/main/source/index.html.md#L19) for an example of usage.
+
+## Version 2.6.1
+
+*May 30, 2020*
+
+* __[security]__ update child dependency activesupport in Gemfile.lock to 5.4.2.3
+* Update Middleman in Gemfile.lock to 4.3.7
+* Replace Travis-CI with GitHub actions for continuous integration
+* Replace Spectrum with GitHub discussions
+
+## Version 2.6.0
+
+*May 18, 2020*
+
+__Note__: 2.5.0 was "pulled" due to a breaking bug discovered after release. It is recommended to skip it, and move straight to 2.6.0.
+
+* Fix large whitespace gap in middle column for sections with codeblocks
+* Fix highlighted code elements having a different background than rest of code block
+* Change JSON keys to have a different font color than their values
+* Disable asset hashing for woff and woff2 elements due to middleman bug breaking woff2 asset hashing in general
+* Move Dockerfile to Debian from Alpine
+* Converted repo to a [GitHub template](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/creating-a-template-repository)
+* Update sassc to 2.3.0 in Gemfile.lock
+
+## Version 2.5.0
+
+*May 8, 2020*
+
+* __[security]__ update nokogiri to ~> 1.10.8
+* Update links in example docs to https://github.com/slatedocs/slate from https://github.com/lord/slate
+* Update LICENSE to include full Apache 2.0 text
+* Test slate against Ruby 2.5 and 2.6 on Travis-CI
+* Update Vagrantfile to use Ubuntu 18.04 (thanks @bradthurber)
+* Parse arguments and flags for deploy.sh on script start, instead of potentially after building source files
+* Install nodejs inside Vagrantfile (thanks @fernandoaguilar)
+* Add Dockerfile for running slate (thanks @redhatxl)
+* update middleman-syntax and rouge to ~>3.2
+* update middleman to 4.3.6
+
+## Version 2.4.0
+
+*October 19, 2019*
+
+- Move repository from lord/slate to slatedocs/slate
+- Fix documentation to point at new repo link, thanks to [Arun](https://github.com/slash-arun), [Gustavo Gawryszewski](https://github.com/gawry), and [Daniel Korbit](https://github.com/danielkorbit)
+- Update `nokogiri` to 1.10.4
+- Update `ffi` in `Gemfile.lock` to fix security warnings, thanks to [Grey Baker](https://github.com/greysteil) and [jakemack](https://github.com/jakemack)
+- Update `rack` to 2.0.7 in `Gemfile.lock` to fix security warnings, thanks to [Grey Baker](https://github.com/greysteil) and [jakemack](https://github.com/jakemack)
+- Update middleman to `4.3` and relax constraints on middleman related gems, thanks to [jakemack](https://github.com/jakemack)
+- Add sass gem, thanks to [jakemack](https://github.com/jakemack)
+- Activate `asset_cache` in middleman to improve cacheability of static files, thanks to [Sam Gilman](https://github.com/thenengah)
+- Update to using bundler 2 for `Gemfile.lock`, thanks to [jakemack](https://github.com/jakemack)
+## Version 2.3.1
+
+*July 5, 2018*
+
+- Update `sprockets` in `Gemfile.lock` to fix security warnings
+
+## Version 2.3
+
+*July 5, 2018*
+
+- Allows strikethrough in markdown by default.
+- Upgrades jQuery to 3.2.1, thanks to [Tomi Takussaari](https://github.com/TomiTakussaari)
+- Fixes invalid HTML in `layout.erb`, thanks to [Eric Scouten](https://github.com/scouten) for pointing out
+- Hopefully fixes Vagrant memory issues, thanks to [Petter Blomberg](https://github.com/p-blomberg) for the suggestion
+- Cleans HTML in headers before setting `document.title`, thanks to [Dan Levy](https://github.com/justsml)
+- Allows trailing whitespace in markdown files, thanks to [Samuel Cousin](https://github.com/kuzyn)
+- Fixes pushState/replaceState problems with scrolling not changing the document hash, thanks to [Andrey Fedorov](https://github.com/anfedorov)
+- Removes some outdated examples, thanks [@al-tr](https://github.com/al-tr), [Jerome Dahdah](https://github.com/jdahdah), and [Ricardo Castro](https://github.com/mccricardo)
+- Fixes `nav-padding` bug, thanks [Jerome Dahdah](https://github.com/jdahdah)
+- Code style fixes thanks to [Sebastian Zaremba](https://github.com/vassyz)
+- Nokogiri version bump thanks to [Grey Baker](https://github.com/greysteil)
+- Fix to default `index.md` text thanks to [Nick Busey](https://github.com/NickBusey)
+
+Thanks to everyone who contributed to this release!
+
+## Version 2.2
+
+*January 19, 2018*
+
+- Fixes bugs with some non-roman languages not generating unique headers
+- Adds editorconfig, thanks to [Jay Thomas](https://github.com/jaythomas)
+- Adds optional `NestingUniqueHeadCounter`, thanks to [Vladimir Morozov](https://github.com/greenhost87)
+- Small fixes to typos and language, thx [Emir Ribić](https://github.com/ribice), [Gregor Martynus](https://github.com/gr2m), and [Martius](https://github.com/martiuslim)!
+- Adds links to Spectrum chat for questions in README and ISSUE_TEMPLATE
+
+## Version 2.1
+
+*October 30, 2017*
+
+- Right-to-left text stylesheet option, thanks to [Mohammad Hossein Rabiee](https://github.com/mhrabiee)
+- Fix for HTML5 history state bug, thanks to [Zach Toolson](https://github.com/ztoolson)
+- Small styling changes, typo fixes, small bug fixes from [Marian Friedmann](https://github.com/rnarian), [Ben Wilhelm](https://github.com/benwilhelm), [Fouad Matin](https://github.com/fouad), [Nicolas Bonduel](https://github.com/NicolasBonduel), [Christian Oliff](https://github.com/coliff)
+
+Thanks to everyone who submitted PRs for this version!
+
+## Version 2.0
+
+*July 17, 2017*
+
+- All-new statically generated table of contents
+ - Should be much faster loading and scrolling for large pages
+ - Smaller Javascript file sizes
+ - Avoids the problem with the last link in the ToC not ever highlighting if the section was shorter than the page
+ - Fixes control-click not opening in a new page
+ - Automatically updates the HTML title as you scroll
+- Updated design
+ - New default colors!
+ - New spacings and sizes!
+ - System-default typefaces, just like GitHub
+- Added search input delay on large corpuses to reduce lag
+- We even bumped the major version cause hey, why not?
+- Various small bug fixes
+
+Thanks to everyone who helped debug or wrote code for this version! It was a serious community effort, and I couldn't have done it alone.
+
+## Version 1.5
+
+*February 23, 2017*
+
+- Add [multiple tabs per programming language](https://github.com/lord/slate/wiki/Multiple-language-tabs-per-programming-language) feature
+- Upgrade Middleman to add Ruby 1.4.0 compatibility
+- Switch default code highlighting color scheme to better highlight JSON
+- Various small typo and bug fixes
+
+## Version 1.4
+
+*November 24, 2016*
+
+- Upgrade Middleman and Rouge gems, should hopefully solve a number of bugs
+- Update some links in README
+- Fix broken Vagrant startup script
+- Fix some problems with deploy.sh help message
+- Fix bug with language tabs not hiding properly if no error
+- Add `!default` to SASS variables
+- Fix bug with logo margin
+- Bump tested Ruby versions in .travis.yml
+
+## Version 1.3.3
+
+*June 11, 2016*
+
+Documentation and example changes.
+
+## Version 1.3.2
+
+*February 3, 2016*
+
+A small bugfix for slightly incorrect background colors on code samples in some cases.
+
+## Version 1.3.1
+
+*January 31, 2016*
+
+A small bugfix for incorrect whitespace in code blocks.
+
+## Version 1.3
+
+*January 27, 2016*
+
+We've upgraded Middleman and a number of other dependencies, which should fix quite a few bugs.
+
+Instead of `rake build` and `rake deploy`, you should now run `bundle exec middleman build --clean` to build your server, and `./deploy.sh` to deploy it to Github Pages.
+
## Version 1.2
-*June 20, 2014*
+*June 20, 2015*
**Fixes:**
@@ -21,7 +257,7 @@
## Version 1.1
-*July 27th, 2014*
+*July 27, 2014*
**Fixes:**
diff --git a/CNAME b/CNAME
new file mode 100644
index 00000000000..a82d59d6031
--- /dev/null
+++ b/CNAME
@@ -0,0 +1 @@
+apidocs.eresourcescheduler.cloud
\ No newline at end of file
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 00000000000..cc17fd98d59
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,46 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at hello@lord.io. The project team will review and investigate all complaints, and will respond in a way that it deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
+
+[homepage]: http://contributor-covenant.org
+[version]: http://contributor-covenant.org/version/1/4/
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
deleted file mode 100644
index b04fc955ca5..00000000000
--- a/CONTRIBUTING.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Contributing to Slate
-
-Thanks for contributing to Slate! A couple of quick guidelines for submitting PRs:
-
-- Please point your pull requests at the `dev` branch, and keep your commit messages clear and informative.
-- Please make sure your contributions work in the most recent version of Chrome, Firefox, and IE.
-- If you're implementing a new feature, even if it's relatively small, it's nice to open an issue before you start so that others know what you're working on and can help make sure you're on the right track.
-
-Thanks again! Happy coding.
\ No newline at end of file
diff --git a/Dockerfile b/Dockerfile
index 8183c7a8b04..504da654d10 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -1,12 +1,29 @@
-FROM ubuntu:trusty
-
-RUN apt-get update
-RUN apt-get install -yq ruby ruby-dev build-essential git
-RUN gem install --no-ri --no-rdoc bundler
-ADD Gemfile /app/Gemfile
-ADD Gemfile.lock /app/Gemfile.lock
-RUN cd /app; bundle install
-ADD . /app
+FROM ruby:2.6-slim
+
+WORKDIR /srv/slate
+
+VOLUME /srv/slate/build
+VOLUME /srv/slate/source
+
EXPOSE 4567
-WORKDIR /app
-CMD ["bundle", "exec", "middleman", "server"]
+
+COPY Gemfile .
+COPY Gemfile.lock .
+
+RUN apt-get update \
+ && apt-get install -y --no-install-recommends \
+ build-essential \
+ git \
+ nodejs \
+ && gem install bundler \
+ && bundle install \
+ && apt-get remove -y build-essential git \
+ && apt-get autoremove -y \
+ && rm -rf /var/lib/apt/lists/*
+
+COPY . /srv/slate
+
+RUN chmod +x /srv/slate/slate.sh
+
+ENTRYPOINT ["/srv/slate/slate.sh"]
+CMD ["build"]
diff --git a/Gemfile b/Gemfile
index 3a2a2e01a82..ce85295a055 100644
--- a/Gemfile
+++ b/Gemfile
@@ -1,12 +1,13 @@
+ruby '>= 2.5'
source 'https://rubygems.org'
# Middleman
-gem 'middleman', '~>3.3.10'
-gem 'middleman-gh-pages', '~> 0.0.3'
-gem 'middleman-syntax', '~> 2.0.0'
-gem 'middleman-autoprefixer', '~> 2.4.4'
-gem 'rouge', '~> 1.9.0'
-gem 'redcarpet', '~> 3.3.1'
-
-gem 'rake', '~> 10.4.2'
-gem 'therubyracer', '~> 0.12.1', platforms: :ruby
+gem 'middleman', :github => 'middleman/middleman', :branch => '4.x'
+gem 'middleman-syntax', '~> 3.2'
+gem 'middleman-autoprefixer', '~> 2.7'
+gem 'middleman-sprockets', '~> 4.1'
+gem 'rouge', '~> 3.21'
+gem 'redcarpet', '~> 3.5.0'
+gem 'nokogiri', '~> 1.11.0'
+gem 'sass'
+gem 'webrick'
\ No newline at end of file
diff --git a/Gemfile.lock b/Gemfile.lock
index f9978492816..e2f55c62802 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -1,140 +1,153 @@
+GIT
+ remote: https://github.com/middleman/middleman.git
+ revision: d180ca337202873f2601310c74ba2b6b4cf063ec
+ branch: 4.x
+ specs:
+ middleman (4.3.11)
+ coffee-script (~> 2.2)
+ haml (>= 4.0.5)
+ kramdown (>= 2.3.0)
+ middleman-cli (= 4.3.11)
+ middleman-core (= 4.3.11)
+ middleman-cli (4.3.11)
+ thor (>= 0.17.0, < 2.0)
+ middleman-core (4.3.11)
+ activesupport (>= 4.2, < 6.1)
+ addressable (~> 2.3)
+ backports (~> 3.6)
+ bundler (~> 2.0)
+ contracts (~> 0.13.0)
+ dotenv
+ erubis
+ execjs (~> 2.0)
+ fast_blank
+ fastimage (~> 2.0)
+ hamster (~> 3.0)
+ hashie (~> 3.4)
+ i18n (~> 0.9.0)
+ listen (~> 3.0.0)
+ memoist (~> 0.14)
+ padrino-helpers (~> 0.13.0)
+ parallel
+ rack (>= 1.4.5, < 3)
+ sassc (~> 2.0)
+ servolux
+ tilt (~> 2.0.9)
+ toml
+ uglifier (~> 3.0)
+ webrick
+
GEM
remote: https://rubygems.org/
specs:
- activesupport (4.1.11)
- i18n (~> 0.6, >= 0.6.9)
- json (~> 1.7, >= 1.7.7)
+ activesupport (6.0.3.6)
+ concurrent-ruby (~> 1.0, >= 1.0.2)
+ i18n (>= 0.7, < 2)
minitest (~> 5.1)
- thread_safe (~> 0.1)
tzinfo (~> 1.1)
- autoprefixer-rails (5.2.0.1)
+ zeitwerk (~> 2.2, >= 2.2.2)
+ addressable (2.7.0)
+ public_suffix (>= 2.0.2, < 5.0)
+ autoprefixer-rails (9.5.1.1)
execjs
- json
- celluloid (0.16.0)
- timers (~> 4.0.0)
- chunky_png (1.3.4)
+ backports (3.21.0)
coffee-script (2.4.1)
coffee-script-source
execjs
- coffee-script-source (1.9.1.1)
- compass (1.0.3)
- chunky_png (~> 1.2)
- compass-core (~> 1.0.2)
- compass-import-once (~> 1.0.5)
- rb-fsevent (>= 0.9.3)
- rb-inotify (>= 0.9)
- sass (>= 3.3.13, < 3.5)
- compass-core (1.0.3)
- multi_json (~> 1.0)
- sass (>= 3.3.0, < 3.5)
- compass-import-once (1.0.5)
- sass (>= 3.2, < 3.5)
+ coffee-script-source (1.12.2)
+ concurrent-ruby (1.1.8)
+ contracts (0.13.0)
+ dotenv (2.7.6)
erubis (2.7.0)
- execjs (2.5.2)
- ffi (1.9.8)
- haml (4.0.6)
+ execjs (2.7.0)
+ fast_blank (1.0.0)
+ fastimage (2.2.3)
+ ffi (1.15.0)
+ haml (5.2.1)
+ temple (>= 0.8.0)
tilt
- hike (1.2.3)
- hitimes (1.2.2)
- hooks (0.4.0)
- uber (~> 0.0.4)
- i18n (0.7.0)
- json (1.8.3)
- kramdown (1.7.0)
- libv8 (3.16.14.7)
- listen (2.10.1)
- celluloid (~> 0.16.0)
- rb-fsevent (>= 0.9.3)
- rb-inotify (>= 0.9)
- middleman (3.3.12)
- coffee-script (~> 2.2)
- compass (>= 1.0.0, < 2.0.0)
- compass-import-once (= 1.0.5)
- execjs (~> 2.0)
- haml (>= 4.0.5)
- kramdown (~> 1.2)
- middleman-core (= 3.3.12)
- middleman-sprockets (>= 3.1.2)
- sass (>= 3.4.0, < 4.0)
- uglifier (~> 2.5)
- middleman-autoprefixer (2.4.4)
- autoprefixer-rails (~> 5.2.0)
+ hamster (3.0.0)
+ concurrent-ruby (~> 1.0)
+ hashie (3.6.0)
+ i18n (0.9.5)
+ concurrent-ruby (~> 1.0)
+ kramdown (2.3.1)
+ rexml
+ listen (3.0.8)
+ rb-fsevent (~> 0.9, >= 0.9.4)
+ rb-inotify (~> 0.9, >= 0.9.7)
+ memoist (0.16.2)
+ middleman-autoprefixer (2.10.1)
+ autoprefixer-rails (~> 9.1)
middleman-core (>= 3.3.3)
- middleman-core (3.3.12)
- activesupport (~> 4.1.0)
- bundler (~> 1.1)
- erubis
- hooks (~> 0.3)
- i18n (~> 0.7.0)
- listen (>= 2.7.9, < 3.0)
- padrino-helpers (~> 0.12.3)
- rack (>= 1.4.5, < 2.0)
- rack-test (~> 0.6.2)
- thor (>= 0.15.2, < 2.0)
- tilt (~> 1.4.1, < 2.0)
- middleman-gh-pages (0.0.3)
- rake (> 0.9.3)
- middleman-sprockets (3.4.2)
- middleman-core (>= 3.3)
- sprockets (~> 2.12.1)
- sprockets-helpers (~> 1.1.0)
- sprockets-sass (~> 1.3.0)
- middleman-syntax (2.0.0)
- middleman-core (~> 3.2)
- rouge (~> 1.0)
- minitest (5.7.0)
- multi_json (1.11.1)
- padrino-helpers (0.12.5)
+ middleman-sprockets (4.1.1)
+ middleman-core (~> 4.0)
+ sprockets (>= 3.0)
+ middleman-syntax (3.2.0)
+ middleman-core (>= 3.2)
+ rouge (~> 3.2)
+ mini_portile2 (2.5.0)
+ minitest (5.14.4)
+ nokogiri (1.11.3)
+ mini_portile2 (~> 2.5.0)
+ racc (~> 1.4)
+ padrino-helpers (0.13.3.4)
i18n (~> 0.6, >= 0.6.7)
- padrino-support (= 0.12.5)
- tilt (~> 1.4.1)
- padrino-support (0.12.5)
+ padrino-support (= 0.13.3.4)
+ tilt (>= 1.4.1, < 3)
+ padrino-support (0.13.3.4)
activesupport (>= 3.1)
- rack (1.6.4)
- rack-test (0.6.3)
- rack (>= 1.0)
- rake (10.4.2)
- rb-fsevent (0.9.5)
- rb-inotify (0.9.5)
- ffi (>= 0.5.0)
- redcarpet (3.3.1)
- ref (1.0.5)
- rouge (1.9.0)
- sass (3.4.14)
- sprockets (2.12.3)
- hike (~> 1.2)
- multi_json (~> 1.0)
- rack (~> 1.0)
- tilt (~> 1.1, != 1.3.0)
- sprockets-helpers (1.1.0)
- sprockets (~> 2.0)
- sprockets-sass (1.3.1)
- sprockets (~> 2.0)
- tilt (~> 1.1)
- therubyracer (0.12.2)
- libv8 (~> 3.16.14.0)
- ref
- thor (0.19.1)
- thread_safe (0.3.5)
- tilt (1.4.1)
- timers (4.0.1)
- hitimes
- tzinfo (1.2.2)
+ parallel (1.20.1)
+ parslet (1.8.2)
+ public_suffix (4.0.6)
+ racc (1.5.2)
+ rack (2.2.3)
+ rb-fsevent (0.10.4)
+ rb-inotify (0.10.1)
+ ffi (~> 1.0)
+ redcarpet (3.5.1)
+ rexml (3.2.5)
+ rouge (3.26.0)
+ sass (3.7.4)
+ sass-listen (~> 4.0.0)
+ sass-listen (4.0.0)
+ rb-fsevent (~> 0.9, >= 0.9.4)
+ rb-inotify (~> 0.9, >= 0.9.7)
+ sassc (2.4.0)
+ ffi (~> 1.9)
+ servolux (0.13.0)
+ sprockets (3.7.2)
+ concurrent-ruby (~> 1.0)
+ rack (> 1, < 3)
+ temple (0.8.2)
+ thor (1.1.0)
+ thread_safe (0.3.6)
+ tilt (2.0.10)
+ toml (0.2.0)
+ parslet (~> 1.8.0)
+ tzinfo (1.2.9)
thread_safe (~> 0.1)
- uber (0.0.13)
- uglifier (2.7.1)
- execjs (>= 0.3.0)
- json (>= 1.8.0)
+ uglifier (3.2.0)
+ execjs (>= 0.3.0, < 3)
+ webrick (1.7.0)
+ zeitwerk (2.4.2)
PLATFORMS
ruby
DEPENDENCIES
- middleman (~> 3.3.10)
- middleman-autoprefixer (~> 2.4.4)
- middleman-gh-pages (~> 0.0.3)
- middleman-syntax (~> 2.0.0)
- rake (~> 10.4.2)
- redcarpet (~> 3.3.1)
- rouge (~> 1.9.0)
- therubyracer (~> 0.12.1)
+ middleman!
+ middleman-autoprefixer (~> 2.7)
+ middleman-sprockets (~> 4.1)
+ middleman-syntax (~> 3.2)
+ nokogiri (~> 1.11.0)
+ redcarpet (~> 3.5.0)
+ rouge (~> 3.21)
+ sass
+ webrick
+
+RUBY VERSION
+ ruby 2.7.2p137
+
+BUNDLED WITH
+ 2.2.15
diff --git a/LICENSE b/LICENSE
index 5ceddf59f68..261eeb9e9f8 100644
--- a/LICENSE
+++ b/LICENSE
@@ -1,13 +1,201 @@
-Copyright 2008-2013 Concur Technologies, Inc.
+ Apache License
+ Version 2.0, January 2004
+ http://www.apache.org/licenses/
-Licensed under the Apache License, Version 2.0 (the "License"); you may
-not use this file except in compliance with the License. You may obtain
-a copy of the License at
+ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
- http://www.apache.org/licenses/LICENSE-2.0
+ 1. Definitions.
-Unless required by applicable law or agreed to in writing, software
-distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
-WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
-License for the specific language governing permissions and limitations
-under the License.
\ No newline at end of file
+ "License" shall mean the terms and conditions for use, reproduction,
+ and distribution as defined by Sections 1 through 9 of this document.
+
+ "Licensor" shall mean the copyright owner or entity authorized by
+ the copyright owner that is granting the License.
+
+ "Legal Entity" shall mean the union of the acting entity and all
+ other entities that control, are controlled by, or are under common
+ control with that entity. For the purposes of this definition,
+ "control" means (i) the power, direct or indirect, to cause the
+ direction or management of such entity, whether by contract or
+ otherwise, or (ii) ownership of fifty percent (50%) or more of the
+ outstanding shares, or (iii) beneficial ownership of such entity.
+
+ "You" (or "Your") shall mean an individual or Legal Entity
+ exercising permissions granted by this License.
+
+ "Source" form shall mean the preferred form for making modifications,
+ including but not limited to software source code, documentation
+ source, and configuration files.
+
+ "Object" form shall mean any form resulting from mechanical
+ transformation or translation of a Source form, including but
+ not limited to compiled object code, generated documentation,
+ and conversions to other media types.
+
+ "Work" shall mean the work of authorship, whether in Source or
+ Object form, made available under the License, as indicated by a
+ copyright notice that is included in or attached to the work
+ (an example is provided in the Appendix below).
+
+ "Derivative Works" shall mean any work, whether in Source or Object
+ form, that is based on (or derived from) the Work and for which the
+ editorial revisions, annotations, elaborations, or other modifications
+ represent, as a whole, an original work of authorship. For the purposes
+ of this License, Derivative Works shall not include works that remain
+ separable from, or merely link (or bind by name) to the interfaces of,
+ the Work and Derivative Works thereof.
+
+ "Contribution" shall mean any work of authorship, including
+ the original version of the Work and any modifications or additions
+ to that Work or Derivative Works thereof, that is intentionally
+ submitted to Licensor for inclusion in the Work by the copyright owner
+ or by an individual or Legal Entity authorized to submit on behalf of
+ the copyright owner. For the purposes of this definition, "submitted"
+ means any form of electronic, verbal, or written communication sent
+ to the Licensor or its representatives, including but not limited to
+ communication on electronic mailing lists, source code control systems,
+ and issue tracking systems that are managed by, or on behalf of, the
+ Licensor for the purpose of discussing and improving the Work, but
+ excluding communication that is conspicuously marked or otherwise
+ designated in writing by the copyright owner as "Not a Contribution."
+
+ "Contributor" shall mean Licensor and any individual or Legal Entity
+ on behalf of whom a Contribution has been received by Licensor and
+ subsequently incorporated within the Work.
+
+ 2. Grant of Copyright License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ copyright license to reproduce, prepare Derivative Works of,
+ publicly display, publicly perform, sublicense, and distribute the
+ Work and such Derivative Works in Source or Object form.
+
+ 3. Grant of Patent License. Subject to the terms and conditions of
+ this License, each Contributor hereby grants to You a perpetual,
+ worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+ (except as stated in this section) patent license to make, have made,
+ use, offer to sell, sell, import, and otherwise transfer the Work,
+ where such license applies only to those patent claims licensable
+ by such Contributor that are necessarily infringed by their
+ Contribution(s) alone or by combination of their Contribution(s)
+ with the Work to which such Contribution(s) was submitted. If You
+ institute patent litigation against any entity (including a
+ cross-claim or counterclaim in a lawsuit) alleging that the Work
+ or a Contribution incorporated within the Work constitutes direct
+ or contributory patent infringement, then any patent licenses
+ granted to You under this License for that Work shall terminate
+ as of the date such litigation is filed.
+
+ 4. Redistribution. You may reproduce and distribute copies of the
+ Work or Derivative Works thereof in any medium, with or without
+ modifications, and in Source or Object form, provided that You
+ meet the following conditions:
+
+ (a) You must give any other recipients of the Work or
+ Derivative Works a copy of this License; and
+
+ (b) You must cause any modified files to carry prominent notices
+ stating that You changed the files; and
+
+ (c) You must retain, in the Source form of any Derivative Works
+ that You distribute, all copyright, patent, trademark, and
+ attribution notices from the Source form of the Work,
+ excluding those notices that do not pertain to any part of
+ the Derivative Works; and
+
+ (d) If the Work includes a "NOTICE" text file as part of its
+ distribution, then any Derivative Works that You distribute must
+ include a readable copy of the attribution notices contained
+ within such NOTICE file, excluding those notices that do not
+ pertain to any part of the Derivative Works, in at least one
+ of the following places: within a NOTICE text file distributed
+ as part of the Derivative Works; within the Source form or
+ documentation, if provided along with the Derivative Works; or,
+ within a display generated by the Derivative Works, if and
+ wherever such third-party notices normally appear. The contents
+ of the NOTICE file are for informational purposes only and
+ do not modify the License. You may add Your own attribution
+ notices within Derivative Works that You distribute, alongside
+ or as an addendum to the NOTICE text from the Work, provided
+ that such additional attribution notices cannot be construed
+ as modifying the License.
+
+ You may add Your own copyright statement to Your modifications and
+ may provide additional or different license terms and conditions
+ for use, reproduction, or distribution of Your modifications, or
+ for any such Derivative Works as a whole, provided Your use,
+ reproduction, and distribution of the Work otherwise complies with
+ the conditions stated in this License.
+
+ 5. Submission of Contributions. Unless You explicitly state otherwise,
+ any Contribution intentionally submitted for inclusion in the Work
+ by You to the Licensor shall be under the terms and conditions of
+ this License, without any additional terms or conditions.
+ Notwithstanding the above, nothing herein shall supersede or modify
+ the terms of any separate license agreement you may have executed
+ with Licensor regarding such Contributions.
+
+ 6. Trademarks. This License does not grant permission to use the trade
+ names, trademarks, service marks, or product names of the Licensor,
+ except as required for reasonable and customary use in describing the
+ origin of the Work and reproducing the content of the NOTICE file.
+
+ 7. Disclaimer of Warranty. Unless required by applicable law or
+ agreed to in writing, Licensor provides the Work (and each
+ Contributor provides its Contributions) on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+ implied, including, without limitation, any warranties or conditions
+ of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+ PARTICULAR PURPOSE. You are solely responsible for determining the
+ appropriateness of using or redistributing the Work and assume any
+ risks associated with Your exercise of permissions under this License.
+
+ 8. Limitation of Liability. In no event and under no legal theory,
+ whether in tort (including negligence), contract, or otherwise,
+ unless required by applicable law (such as deliberate and grossly
+ negligent acts) or agreed to in writing, shall any Contributor be
+ liable to You for damages, including any direct, indirect, special,
+ incidental, or consequential damages of any character arising as a
+ result of this License or out of the use or inability to use the
+ Work (including but not limited to damages for loss of goodwill,
+ work stoppage, computer failure or malfunction, or any and all
+ other commercial damages or losses), even if such Contributor
+ has been advised of the possibility of such damages.
+
+ 9. Accepting Warranty or Additional Liability. While redistributing
+ the Work or Derivative Works thereof, You may choose to offer,
+ and charge a fee for, acceptance of support, warranty, indemnity,
+ or other liability obligations and/or rights consistent with this
+ License. However, in accepting such obligations, You may act only
+ on Your own behalf and on Your sole responsibility, not on behalf
+ of any other Contributor, and only if You agree to indemnify,
+ defend, and hold each Contributor harmless for any liability
+ incurred by, or claims asserted against, such Contributor by reason
+ of your accepting any such warranty or additional liability.
+
+ END OF TERMS AND CONDITIONS
+
+ APPENDIX: How to apply the Apache License to your work.
+
+ To apply the Apache License to your work, attach the following
+ boilerplate notice, with the fields enclosed by brackets "[]"
+ replaced with your own identifying information. (Don't include
+ the brackets!) The text should be enclosed in the appropriate
+ comment syntax for the file format. We also recommend that a
+ file or class name and description of purpose be included on the
+ same "printed page" as the copyright notice for easier
+ identification within third-party archives.
+
+ Copyright [yyyy] [name of copyright owner]
+
+ Licensed under the Apache License, Version 2.0 (the "License");
+ you may not use this file except in compliance with the License.
+ You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+ Unless required by applicable law or agreed to in writing, software
+ distributed under the License is distributed on an "AS IS" BASIS,
+ WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ See the License for the specific language governing permissions and
+ limitations under the License.
diff --git a/README.md b/README.md
index efb7e1eb8cd..2744e63b7a8 100644
--- a/README.md
+++ b/README.md
@@ -1,122 +1,81 @@
-Slate
-========
+
Features
------------
-* **Clean, intuitive design** — with Slate, the description of your API is on the left side of your documentation, and all the code examples are on the right side. Inspired by [Stripe's](https://stripe.com/docs/api) and [Paypal's](https://developer.paypal.com/webapps/developer/docs/api/) API docs. Slate is responsive, so it looks great on tablets, phones, and even print.
+* **Clean, intuitive design** — With Slate, the description of your API is on the left side of your documentation, and all the code examples are on the right side. Inspired by [Stripe's](https://stripe.com/docs/api) and [PayPal's](https://developer.paypal.com/webapps/developer/docs/api/) API docs. Slate is responsive, so it looks great on tablets, phones, and even in print.
-* **Everything on a single page** — gone are the days where your users had to search through a million pages to find what they wanted. Slate puts the entire documentation on a single page. We haven't sacrificed linkability, though. As you scroll, your browser's hash will update to the nearest header, so linking to a particular point in the documentation is still natural and easy.
+* **Everything on a single page** — Gone are the days when your users had to search through a million pages to find what they wanted. Slate puts the entire documentation on a single page. We haven't sacrificed linkability, though. As you scroll, your browser's hash will update to the nearest header, so linking to a particular point in the documentation is still natural and easy.
-* **Slate is just Markdown** — when you write docs with Slate, you're just writing Markdown, which makes it simple to edit and understand. Everything is written in Markdown — even the code samples are just Markdown code blocks!
+* **Slate is just Markdown** — When you write docs with Slate, you're just writing Markdown, which makes it simple to edit and understand. Everything is written in Markdown — even the code samples are just Markdown code blocks.
-* **Write code samples in multiple languages** — if your API has bindings in multiple programming languages, you easily put in tabs to switch between them. In your document, you'll distinguish different languages by specifying the language name at the top of each code block, just like with Github Flavored Markdown!
+* **Write code samples in multiple languages** — If your API has bindings in multiple programming languages, you can easily put in tabs to switch between them. In your document, you'll distinguish different languages by specifying the language name at the top of each code block, just like with GitHub Flavored Markdown.
-* **Out-of-the-box syntax highlighting** for [almost 60 languages](http://rouge.jayferd.us/demo), no configuration required.
+* **Out-of-the-box syntax highlighting** for [over 100 languages](https://github.com/rouge-ruby/rouge/wiki/List-of-supported-languages-and-lexers), no configuration required.
* **Automatic, smoothly scrolling table of contents** on the far left of the page. As you scroll, it displays your current position in the document. It's fast, too. We're using Slate at TripIt to build documentation for our new API, where our table of contents has over 180 entries. We've made sure that the performance remains excellent, even for larger documents.
-* **Let your users update your documentation for you** — by default, your Slate-generated documentation is hosted in a public Github repository. Not only does this mean you get free hosting for your docs with Github Pages, but it also makes it's simple for other developers to make pull requests to your docs if they find typos or other problems. Of course, if you don't want to, you're welcome to not use Github and host your docs elsewhere!
+* **Let your users update your documentation for you** — By default, your Slate-generated documentation is hosted in a public GitHub repository. Not only does this mean you get free hosting for your docs with GitHub Pages, but it also makes it simple for other developers to make pull requests to your docs if they find typos or other problems. Of course, if you don't want to use GitHub, you're also welcome to host your docs elsewhere.
-Getting starting with Slate is super easy! Simply fork this repository, and then follow the instructions below. Or, if you'd like to check out what Slate is capable of, take a look at the [sample docs](http://tripit.github.io/slate).
+* **RTL Support** Full right-to-left layout for RTL languages such as Arabic, Persian (Farsi), Hebrew etc.
-
+Getting started with Slate is super easy! Simply press the green "use this template" button above and follow the instructions below. Or, if you'd like to check out what Slate is capable of, take a look at the [sample docs](https://slatedocs.github.io/slate/).
Getting Started with Slate
------------------------------
-### Prerequisites
-
-You're going to need:
-
- - **Linux or OS X** — Windows may work, but is unsupported.
- - **Ruby, version 1.9.3 or newer**
- - **Bundler** — If Ruby is already installed, but the `bundle` command doesn't work, just run `gem install bundler` in a terminal.
-
-### Getting Set Up
-
- 1. Fork this repository on Github.
- 2. Clone *your forked repository* (not our original one) to your hard drive with `git clone https://github.com/YOURUSERNAME/slate.git`
- 3. `cd slate`
- 4. Install all dependencies: `bundle install`
- 5. Start the test server: `bundle exec middleman server`
-
-Or use the included Dockerfile! (must install Docker first)
+To get started with Slate, please check out the [Getting Started](https://github.com/slatedocs/slate/wiki#getting-started)
+section in our [wiki](https://github.com/slatedocs/slate/wiki).
-```shell
-docker build -t slate .
-docker run -d -p 4567:4567 slate
-```
+We support running Slate in three different ways:
+* [Natively](https://github.com/slatedocs/slate/wiki/Using-Slate-Natively)
+* [Using Vagrant](https://github.com/slatedocs/slate/wiki/Using-Slate-in-Vagrant)
+* [Using Docker](https://github.com/slatedocs/slate/wiki/Using-Slate-in-Docker)
-You can now see the docs at . Whoa! That was fast!
-
-*Note: if you're using the Docker setup on OSX, the docs will be
-availalable at the output of `boot2docker ip` instead of `localhost:4567`.*
+Companies Using Slate
+---------------------------------
-Now that Slate is all set up your machine, you'll probably want to learn more about [editing Slate markdown](https://github.com/tripit/slate/wiki/Markdown-Syntax), or [how to publish your docs](https://github.com/tripit/slate/wiki/Deploying-Slate).
+* [NASA](https://api.nasa.gov)
+* [Sony](http://developers.cimediacloud.com)
+* [Best Buy](https://bestbuyapis.github.io/api-documentation/)
+* [Travis-CI](https://docs.travis-ci.com/api/)
+* [Greenhouse](https://developers.greenhouse.io/harvest.html)
+* [WooCommerce](http://woocommerce.github.io/woocommerce-rest-api-docs/)
+* [Dwolla](https://docs.dwolla.com/)
+* [Clearbit](https://clearbit.com/docs)
+* [Coinbase](https://developers.coinbase.com/api)
+* [Parrot Drones](http://developer.parrot.com/docs/bebop/)
-Examples of Slate in the Wild
----------------------------------
+You can view more in [the list on the wiki](https://github.com/slatedocs/slate/wiki/Slate-in-the-Wild).
-* [Travis-CI's API docs](http://docs.travis-ci.com/api/)
-* [Mozilla's localForage docs](http://mozilla.github.io/localForage/)
-* [Mozilla Recroom](http://mozilla.github.io/recroom/)
-* [ChaiOne Gameplan API docs](http://chaione.github.io/gameplanb2b/#introduction)
-* [Drcaban's Build a Quine tutorial](http://drcabana.github.io/build-a-quine/#introduction)
-* [PricePlow API docs](https://www.priceplow.com/api/documentation)
-* [Emerging Threats API docs](http://apidocs.emergingthreats.net/)
-* [Appium docs](http://appium.io/slate/en/master)
-* [Golazon Developer](http://developer.golazon.com)
-* [Dwolla API docs](https://docs.dwolla.com/)
-* [RozpisyZapasu API docs](http://www.rozpisyzapasu.cz/dev/api/)
-* [Codestar Framework Docs](http://codestarframework.com/documentation/)
-* [Buddycloud API](http://buddycloud.com/api)
-* [Crafty Clicks API](https://craftyclicks.co.uk/api/)
-* [Paracel API Reference](http://paracel.io/docs/api_reference.html)
-* [Switch Payments Documentation](http://switchpayments.com/docs/) & [API](http://switchpayments.com/developers/)
-* [Coinbase API Reference](https://developers.coinbase.com/api)
-* [Whispir.io API](https://whispir.github.io/api)
-* [NASA API](https://data.nasa.gov/developer/external/planetary/)
-* [CardPay API](https://developers.cardpay.com/)
-* [IBM Cloudant](https://docs-testb.cloudant.com/content-review/_design/couchapp/index.html)
-* [Bitrix basis components](http://bbc.bitrix.expert/)
-* [viagogo API Documentation](http://developer.viagogo.net/)
-* [Fidor Bank API Documentation](http://docs.fidor.de/)
-* [Market Prophit API Documentation](http://developer.marketprophit.com/)
-
-(Feel free to add your site to this list in a pull request!)
-
-Need Help? Found a bug?
+Questions? Need Help? Found a bug?
--------------------
-Just [submit a issue](https://github.com/tripit/slate/issues) to the Slate Github if you need any help. And, of course, feel free to submit pull requests with bug fixes or changes.
+If you've got questions about setup, deploying, special feature implementation in your fork, or just want to chat with the developer, please feel free to [start a thread in our Discussions tab](https://github.com/slatedocs/slate/discussions)!
+Found a bug with upstream Slate? Go ahead and [submit an issue](https://github.com/slatedocs/slate/issues). And, of course, feel free to submit pull requests with bug fixes or changes to the `dev` branch.
Contributors
--------------------
-Slate was built by [Robert Lord](https://lord.io) while at [TripIt](http://tripit.com).
+Slate was built by [Robert Lord](https://lord.io) while at [TripIt](https://www.tripit.com/). The project is now maintained by [Matthew Peveler](https://github.com/MasterOdin) and [Mike Ralphson](https://github.com/MikeRalphson).
Thanks to the following people who have submitted major pull requests:
- [@chrissrogers](https://github.com/chrissrogers)
- [@bootstraponline](https://github.com/bootstraponline)
- [@realityking](https://github.com/realityking)
+- [@cvkef](https://github.com/cvkef)
-Also, thanks to [Sauce Labs](http://saucelabs.com) for helping sponsor the project.
-
-Special Thanks
---------------------
-- [Middleman](https://github.com/middleman/middleman)
-- [jquery.tocify.js](https://github.com/gfranko/jquery.tocify.js)
-- [middleman-syntax](https://github.com/middleman/middleman-syntax)
-- [middleman-gh-pages](https://github.com/neo/middleman-gh-pages)
-- [Font Awesome](http://fortawesome.github.io/Font-Awesome/)
+Also, thanks to [Sauce Labs](http://saucelabs.com) for sponsoring the development of the responsive styles.
diff --git a/Rakefile b/Rakefile
deleted file mode 100644
index 6a952e1e914..00000000000
--- a/Rakefile
+++ /dev/null
@@ -1,6 +0,0 @@
-require 'middleman-gh-pages'
-require 'rake/clean'
-
-CLOBBER.include('build')
-
-task :default => [:build]
diff --git a/Vagrantfile b/Vagrantfile
new file mode 100644
index 00000000000..200839d0222
--- /dev/null
+++ b/Vagrantfile
@@ -0,0 +1,47 @@
+Vagrant.configure(2) do |config|
+ config.vm.box = "ubuntu/bionic64"
+ config.vm.network :forwarded_port, guest: 4567, host: 4567
+ config.vm.provider "virtualbox" do |vb|
+ vb.memory = "2048"
+ end
+
+ config.vm.provision "bootstrap",
+ type: "shell",
+ inline: <<-SHELL
+ # add nodejs v12 repository
+ curl -sL https://deb.nodesource.com/setup_12.x | sudo -E bash -
+
+ sudo apt-get update
+ sudo apt-get install -yq ruby ruby-dev
+ sudo apt-get install -yq pkg-config build-essential nodejs git libxml2-dev libxslt-dev
+ sudo apt-get autoremove -yq
+ gem install --no-ri --no-rdoc bundler
+ SHELL
+
+ # add the local user git config to the vm
+ config.vm.provision "file", source: "~/.gitconfig", destination: ".gitconfig"
+
+ config.vm.provision "install",
+ type: "shell",
+ privileged: false,
+ inline: <<-SHELL
+ echo "=============================================="
+ echo "Installing app dependencies"
+ cd /vagrant
+ sudo gem install bundler -v "$(grep -A 1 "BUNDLED WITH" Gemfile.lock | tail -n 1)"
+ bundle config build.nokogiri --use-system-libraries
+ bundle install
+ SHELL
+
+ config.vm.provision "run",
+ type: "shell",
+ privileged: false,
+ run: "always",
+ inline: <<-SHELL
+ echo "=============================================="
+ echo "Starting up middleman at http://localhost:4567"
+ echo "If it does not come up, check the ~/middleman.log file for any error messages"
+ cd /vagrant
+ bundle exec middleman server --watcher-force-polling --watcher-latency=1 &> ~/middleman.log &
+ SHELL
+end
diff --git a/config.rb b/config.rb
index 43bceaa5a43..6f8b677f617 100644
--- a/config.rb
+++ b/config.rb
@@ -1,3 +1,6 @@
+# Unique header generation
+require './lib/unique_head.rb'
+
# Markdown
set :markdown_engine, :redcarpet
set :markdown,
@@ -5,9 +8,11 @@
smartypants: true,
disable_indented_code_blocks: true,
prettify: true,
+ strikethrough: true,
tables: true,
with_toc_data: true,
- no_intra_emphasis: true
+ no_intra_emphasis: true,
+ renderer: UniqueHeadCounter
# Assets
set :css_dir, 'stylesheets'
@@ -17,6 +22,12 @@
# Activate the syntax highlighter
activate :syntax
+ready do
+ require './lib/monokai_sublime_slate.rb'
+ require './lib/multilang.rb'
+end
+
+activate :sprockets
activate :autoprefixer do |config|
config.browsers = ['last 2 version', 'Firefox ESR']
@@ -30,9 +41,23 @@
# Build Configuration
configure :build do
+ # We do want to hash woff and woff2 as there's a bug where woff2 will use
+ # woff asset hash which breaks things. Trying to use a combination of ignore and
+ # rewrite_ignore does not work as it conflicts weirdly with relative_assets. Disabling
+ # the .woff2 extension only does not work as .woff will still activate it so have to
+ # have both. See https://github.com/slatedocs/slate/issues/1171 for more details.
+ activate :asset_hash, :exts => app.config[:asset_extensions] - %w[.woff .woff2]
+ # If you're having trouble with Middleman hanging, commenting
+ # out the following two lines has been known to help
activate :minify_css
activate :minify_javascript
- # activate :relative_assets
- # activate :asset_hash
# activate :gzip
end
+
+# Deploy Configuration
+# If you want Middleman to listen on a different port, you can set that below
+set :port, 4567
+
+helpers do
+ require './lib/toc_data.rb'
+end
diff --git a/deploy.sh b/deploy.sh
new file mode 100755
index 00000000000..9c0b795ae7d
--- /dev/null
+++ b/deploy.sh
@@ -0,0 +1,229 @@
+#!/usr/bin/env bash
+set -o errexit #abort if any command fails
+me=$(basename "$0")
+
+help_message="\
+Usage: $me [-c FILE] []
+Deploy generated files to a git branch.
+
+Options:
+
+ -h, --help Show this help information.
+ -v, --verbose Increase verbosity. Useful for debugging.
+ -e, --allow-empty Allow deployment of an empty directory.
+ -m, --message MESSAGE Specify the message used when committing on the
+ deploy branch.
+ -n, --no-hash Don't append the source commit's hash to the deploy
+ commit's message.
+ --source-only Only build but not push
+ --push-only Only push but not build
+"
+
+
+run_build() {
+ bundle exec middleman build
+}
+
+parse_args() {
+ # Set args from a local environment file.
+ if [ -e ".env" ]; then
+ source .env
+ fi
+
+ # Parse arg flags
+ # If something is exposed as an environment variable, set/overwrite it
+ # here. Otherwise, set/overwrite the internal variable instead.
+ while : ; do
+ if [[ $1 = "-h" || $1 = "--help" ]]; then
+ echo "$help_message"
+ exit 0
+ elif [[ $1 = "-v" || $1 = "--verbose" ]]; then
+ verbose=true
+ shift
+ elif [[ $1 = "-e" || $1 = "--allow-empty" ]]; then
+ allow_empty=true
+ shift
+ elif [[ ( $1 = "-m" || $1 = "--message" ) && -n $2 ]]; then
+ commit_message=$2
+ shift 2
+ elif [[ $1 = "-n" || $1 = "--no-hash" ]]; then
+ GIT_DEPLOY_APPEND_HASH=false
+ shift
+ elif [[ $1 = "--source-only" ]]; then
+ source_only=true
+ shift
+ elif [[ $1 = "--push-only" ]]; then
+ push_only=true
+ shift
+ else
+ break
+ fi
+ done
+
+ if [ ${source_only} ] && [ ${push_only} ]; then
+ >&2 echo "You can only specify one of --source-only or --push-only"
+ exit 1
+ fi
+
+ # Set internal option vars from the environment and arg flags. All internal
+ # vars should be declared here, with sane defaults if applicable.
+
+ # Source directory & target branch.
+ deploy_directory=build
+ deploy_branch=gh-pages
+
+ #if no user identity is already set in the current git environment, use this:
+ default_username=${GIT_DEPLOY_USERNAME:-deploy.sh}
+ default_email=${GIT_DEPLOY_EMAIL:-}
+
+ #repository to deploy to. must be readable and writable.
+ repo=origin
+
+ #append commit hash to the end of message by default
+ append_hash=${GIT_DEPLOY_APPEND_HASH:-true}
+}
+
+main() {
+ enable_expanded_output
+
+ if ! git diff --exit-code --quiet --cached; then
+ echo Aborting due to uncommitted changes in the index >&2
+ return 1
+ fi
+
+ commit_title=`git log -n 1 --format="%s" HEAD`
+ commit_hash=` git log -n 1 --format="%H" HEAD`
+
+ #default commit message uses last title if a custom one is not supplied
+ if [[ -z $commit_message ]]; then
+ commit_message="publish: $commit_title"
+ fi
+
+ #append hash to commit message unless no hash flag was found
+ if [ $append_hash = true ]; then
+ commit_message="$commit_message"$'\n\n'"generated from commit $commit_hash"
+ fi
+
+ previous_branch=`git rev-parse --abbrev-ref HEAD`
+
+ if [ ! -d "$deploy_directory" ]; then
+ echo "Deploy directory '$deploy_directory' does not exist. Aborting." >&2
+ return 1
+ fi
+
+ # must use short form of flag in ls for compatibility with macOS and BSD
+ if [[ -z `ls -A "$deploy_directory" 2> /dev/null` && -z $allow_empty ]]; then
+ echo "Deploy directory '$deploy_directory' is empty. Aborting. If you're sure you want to deploy an empty tree, use the --allow-empty / -e flag." >&2
+ return 1
+ fi
+
+ if git ls-remote --exit-code $repo "refs/heads/$deploy_branch" ; then
+ # deploy_branch exists in $repo; make sure we have the latest version
+
+ disable_expanded_output
+ git fetch --force $repo $deploy_branch:$deploy_branch
+ enable_expanded_output
+ fi
+
+ # Copy cname record to build directory
+ cp CNAME "$deploy_directory/"
+
+ # check if deploy_branch exists locally
+ if git show-ref --verify --quiet "refs/heads/$deploy_branch"
+ then incremental_deploy
+ else initial_deploy
+ fi
+
+ restore_head
+}
+
+initial_deploy() {
+ git --work-tree "$deploy_directory" checkout --orphan $deploy_branch
+ git --work-tree "$deploy_directory" add --all
+ commit+push
+}
+
+incremental_deploy() {
+ #make deploy_branch the current branch
+ git symbolic-ref HEAD refs/heads/$deploy_branch
+ #put the previously committed contents of deploy_branch into the index
+ git --work-tree "$deploy_directory" reset --mixed --quiet
+ git --work-tree "$deploy_directory" add --all
+
+ set +o errexit
+ diff=$(git --work-tree "$deploy_directory" diff --exit-code --quiet HEAD --)$?
+ set -o errexit
+ case $diff in
+ 0) echo No changes to files in $deploy_directory. Skipping commit.;;
+ 1) commit+push;;
+ *)
+ echo git diff exited with code $diff. Aborting. Staying on branch $deploy_branch so you can debug. To switch back to main, use: git symbolic-ref HEAD refs/heads/main && git reset --mixed >&2
+ return $diff
+ ;;
+ esac
+}
+
+commit+push() {
+ set_user_id
+ git --work-tree "$deploy_directory" commit -m "$commit_message"
+
+ disable_expanded_output
+ #--quiet is important here to avoid outputting the repo URL, which may contain a secret token
+ git push --quiet $repo $deploy_branch
+ enable_expanded_output
+}
+
+#echo expanded commands as they are executed (for debugging)
+enable_expanded_output() {
+ if [ $verbose ]; then
+ set -o xtrace
+ set +o verbose
+ fi
+}
+
+#this is used to avoid outputting the repo URL, which may contain a secret token
+disable_expanded_output() {
+ if [ $verbose ]; then
+ set +o xtrace
+ set -o verbose
+ fi
+}
+
+set_user_id() {
+ if [[ -z `git config user.name` ]]; then
+ git config user.name "$default_username"
+ fi
+ if [[ -z `git config user.email` ]]; then
+ git config user.email "$default_email"
+ fi
+}
+
+restore_head() {
+ if [[ $previous_branch = "HEAD" ]]; then
+ #we weren't on any branch before, so just set HEAD back to the commit it was on
+ git update-ref --no-deref HEAD $commit_hash $deploy_branch
+ else
+ git symbolic-ref HEAD refs/heads/$previous_branch
+ fi
+
+ git reset --mixed
+}
+
+filter() {
+ sed -e "s|$repo|\$repo|g"
+}
+
+sanitize() {
+ "$@" 2> >(filter 1>&2) | filter
+}
+
+parse_args "$@"
+
+if [[ ${source_only} ]]; then
+ run_build
+elif [[ ${push_only} ]]; then
+ main "$@"
+else
+ run_build
+ main "$@"
+fi
diff --git a/lib/monokai_sublime_slate.rb b/lib/monokai_sublime_slate.rb
new file mode 100644
index 00000000000..cd2de33172d
--- /dev/null
+++ b/lib/monokai_sublime_slate.rb
@@ -0,0 +1,95 @@
+# -*- coding: utf-8 -*- #
+# frozen_string_literal: true
+
+# this is based on https://github.com/rouge-ruby/rouge/blob/master/lib/rouge/themes/monokai_sublime.rb
+# but without the added background, and changed styling for JSON keys to be soft_yellow instead of white
+
+module Rouge
+ module Themes
+ class MonokaiSublimeSlate < CSSTheme
+ name 'monokai.sublime.slate'
+
+ palette :black => '#000000'
+ palette :bright_green => '#a6e22e'
+ palette :bright_pink => '#f92672'
+ palette :carmine => '#960050'
+ palette :dark => '#49483e'
+ palette :dark_grey => '#888888'
+ palette :dark_red => '#aa0000'
+ palette :dimgrey => '#75715e'
+ palette :emperor => '#555555'
+ palette :grey => '#999999'
+ palette :light_grey => '#aaaaaa'
+ palette :light_violet => '#ae81ff'
+ palette :soft_cyan => '#66d9ef'
+ palette :soft_yellow => '#e6db74'
+ palette :very_dark => '#1e0010'
+ palette :whitish => '#f8f8f2'
+ palette :orange => '#f6aa11'
+ palette :white => '#ffffff'
+
+ style Generic::Heading, :fg => :grey
+ style Literal::String::Regex, :fg => :orange
+ style Generic::Output, :fg => :dark_grey
+ style Generic::Prompt, :fg => :emperor
+ style Generic::Strong, :bold => false
+ style Generic::Subheading, :fg => :light_grey
+ style Name::Builtin, :fg => :orange
+ style Comment::Multiline,
+ Comment::Preproc,
+ Comment::Single,
+ Comment::Special,
+ Comment, :fg => :dimgrey
+ style Error,
+ Generic::Error,
+ Generic::Traceback, :fg => :carmine
+ style Generic::Deleted,
+ Generic::Inserted,
+ Generic::Emph, :fg => :dark
+ style Keyword::Constant,
+ Keyword::Declaration,
+ Keyword::Reserved,
+ Name::Constant,
+ Keyword::Type, :fg => :soft_cyan
+ style Literal::Number::Float,
+ Literal::Number::Hex,
+ Literal::Number::Integer::Long,
+ Literal::Number::Integer,
+ Literal::Number::Oct,
+ Literal::Number,
+ Literal::String::Char,
+ Literal::String::Escape,
+ Literal::String::Symbol, :fg => :light_violet
+ style Literal::String::Doc,
+ Literal::String::Double,
+ Literal::String::Backtick,
+ Literal::String::Heredoc,
+ Literal::String::Interpol,
+ Literal::String::Other,
+ Literal::String::Single,
+ Literal::String, :fg => :soft_yellow
+ style Name::Attribute,
+ Name::Class,
+ Name::Decorator,
+ Name::Exception,
+ Name::Function, :fg => :bright_green
+ style Name::Variable::Class,
+ Name::Namespace,
+ Name::Entity,
+ Name::Builtin::Pseudo,
+ Name::Variable::Global,
+ Name::Variable::Instance,
+ Name::Variable,
+ Text::Whitespace,
+ Text,
+ Name, :fg => :white
+ style Name::Label, :fg => :bright_pink
+ style Operator::Word,
+ Name::Tag,
+ Keyword,
+ Keyword::Namespace,
+ Keyword::Pseudo,
+ Operator, :fg => :bright_pink
+ end
+ end
+ end
diff --git a/lib/multilang.rb b/lib/multilang.rb
new file mode 100644
index 00000000000..36fbe5b1f07
--- /dev/null
+++ b/lib/multilang.rb
@@ -0,0 +1,16 @@
+module Multilang
+ def block_code(code, full_lang_name)
+ if full_lang_name
+ parts = full_lang_name.split('--')
+ rouge_lang_name = (parts) ? parts[0] : "" # just parts[0] here causes null ref exception when no language specified
+ super(code, rouge_lang_name).sub("highlight #{rouge_lang_name}") do |match|
+ match + " tab-" + full_lang_name
+ end
+ else
+ super(code, full_lang_name)
+ end
+ end
+end
+
+require 'middleman-core/renderers/redcarpet'
+Middleman::Renderers::MiddlemanRedcarpetHTML.send :include, Multilang
diff --git a/lib/nesting_unique_head.rb b/lib/nesting_unique_head.rb
new file mode 100644
index 00000000000..01278371c17
--- /dev/null
+++ b/lib/nesting_unique_head.rb
@@ -0,0 +1,22 @@
+# Nested unique header generation
+require 'middleman-core/renderers/redcarpet'
+
+class NestingUniqueHeadCounter < Middleman::Renderers::MiddlemanRedcarpetHTML
+ def initialize
+ super
+ @@headers_history = {} if !defined?(@@headers_history)
+ end
+
+ def header(text, header_level)
+ friendly_text = text.gsub(/<[^>]*>/,"").parameterize
+ @@headers_history[header_level] = text.parameterize
+
+ if header_level > 1
+ for i in (header_level - 1).downto(1)
+ friendly_text.prepend("#{@@headers_history[i]}-") if @@headers_history.key?(i)
+ end
+ end
+
+ return "#{text}"
+ end
+end
diff --git a/lib/toc_data.rb b/lib/toc_data.rb
new file mode 100644
index 00000000000..4a04efee26f
--- /dev/null
+++ b/lib/toc_data.rb
@@ -0,0 +1,31 @@
+require 'nokogiri'
+
+def toc_data(page_content)
+ html_doc = Nokogiri::HTML::DocumentFragment.parse(page_content)
+
+ # get a flat list of headers
+ headers = []
+ html_doc.css('h1, h2, h3').each do |header|
+ headers.push({
+ id: header.attribute('id').to_s,
+ content: header.children,
+ title: header.children.to_s.gsub(/<[^>]*>/, ''),
+ level: header.name[1].to_i,
+ children: []
+ })
+ end
+
+ [3,2].each do |header_level|
+ header_to_nest = nil
+ headers = headers.reject do |header|
+ if header[:level] == header_level
+ header_to_nest[:children].push header if header_to_nest
+ true
+ else
+ header_to_nest = header if header[:level] < header_level
+ false
+ end
+ end
+ end
+ headers
+end
diff --git a/lib/unique_head.rb b/lib/unique_head.rb
new file mode 100644
index 00000000000..d42bab2aa9d
--- /dev/null
+++ b/lib/unique_head.rb
@@ -0,0 +1,24 @@
+# Unique header generation
+require 'middleman-core/renderers/redcarpet'
+require 'digest'
+class UniqueHeadCounter < Middleman::Renderers::MiddlemanRedcarpetHTML
+ def initialize
+ super
+ @head_count = {}
+ end
+ def header(text, header_level)
+ friendly_text = text.gsub(/<[^>]*>/,"").parameterize
+ if friendly_text.strip.length == 0
+ # Looks like parameterize removed the whole thing! It removes many unicode
+ # characters like Chinese and Russian. To get a unique URL, let's just
+ # URI escape the whole header
+ friendly_text = Digest::SHA1.hexdigest(text)[0,10]
+ end
+ @head_count[friendly_text] ||= 0
+ @head_count[friendly_text] += 1
+ if @head_count[friendly_text] > 1
+ friendly_text += "-#{@head_count[friendly_text]}"
+ end
+ return "#{text}"
+ end
+end
diff --git a/package-lock.json b/package-lock.json
new file mode 100644
index 00000000000..43de595a3de
--- /dev/null
+++ b/package-lock.json
@@ -0,0 +1,6 @@
+{
+ "name": "slate",
+ "lockfileVersion": 3,
+ "requires": true,
+ "packages": {}
+}
diff --git a/slate.sh b/slate.sh
new file mode 100755
index 00000000000..a3cc498e99a
--- /dev/null
+++ b/slate.sh
@@ -0,0 +1,248 @@
+#!/usr/bin/env bash
+set -o errexit #abort if any command fails
+
+me=$(basename "$0")
+
+help_message="\
+Usage: $me [] []
+Run commands related to the slate process.
+
+Commands:
+
+ serve Run the middleman server process, useful for
+ development.
+ build Run the build process.
+ deploy Will build and deploy files to branch. Use
+ --no-build to only deploy.
+
+Global Options:
+
+ -h, --help Show this help information.
+ -v, --verbose Increase verbosity. Useful for debugging.
+
+Deploy options:
+ -e, --allow-empty Allow deployment of an empty directory.
+ -m, --message MESSAGE Specify the message used when committing on the
+ deploy branch.
+ -n, --no-hash Don't append the source commit's hash to the deploy
+ commit's message.
+ --no-build Do not build the source files.
+"
+
+
+run_serve() {
+ exec bundle exec middleman serve --watcher-force-polling
+}
+
+run_build() {
+ bundle exec middleman build --clean
+}
+
+parse_args() {
+ # Set args from a local environment file.
+ if [ -e ".env" ]; then
+ source .env
+ fi
+
+ command=
+
+ # Parse arg flags
+ # If something is exposed as an environment variable, set/overwrite it
+ # here. Otherwise, set/overwrite the internal variable instead.
+ while : ; do
+ if [[ $1 = "-h" || $1 = "--help" ]]; then
+ echo "$help_message"
+ exit 0
+ elif [[ $1 = "-v" || $1 = "--verbose" ]]; then
+ verbose=true
+ shift
+ elif [[ $1 = "-e" || $1 = "--allow-empty" ]]; then
+ allow_empty=true
+ shift
+ elif [[ ( $1 = "-m" || $1 = "--message" ) && -n $2 ]]; then
+ commit_message=$2
+ shift 2
+ elif [[ $1 = "-n" || $1 = "--no-hash" ]]; then
+ GIT_DEPLOY_APPEND_HASH=false
+ shift
+ elif [[ $1 = "--no-build" ]]; then
+ no_build=true
+ shift
+ elif [[ $1 = "serve" || $1 = "build" || $1 = "deploy" ]]; then
+ if [ ! -z "${command}" ]; then
+ >&2 echo "You can only specify one command."
+ exit 1
+ fi
+ command=$1
+ shift
+ elif [ -z $1 ]; then
+ break
+ fi
+ done
+
+ if [ -z "${command}" ]; then
+ >&2 echo "Command not specified."
+ exit 1
+ fi
+
+ # Set internal option vars from the environment and arg flags. All internal
+ # vars should be declared here, with sane defaults if applicable.
+
+ # Source directory & target branch.
+ deploy_directory=build
+ deploy_branch=gh-pages
+
+ #if no user identity is already set in the current git environment, use this:
+ default_username=${GIT_DEPLOY_USERNAME:-deploy.sh}
+ default_email=${GIT_DEPLOY_EMAIL:-}
+
+ #repository to deploy to. must be readable and writable.
+ repo=origin
+
+ #append commit hash to the end of message by default
+ append_hash=${GIT_DEPLOY_APPEND_HASH:-true}
+}
+
+main() {
+ enable_expanded_output
+
+ if ! git diff --exit-code --quiet --cached; then
+ echo Aborting due to uncommitted changes in the index >&2
+ return 1
+ fi
+
+ commit_title=`git log -n 1 --format="%s" HEAD`
+ commit_hash=` git log -n 1 --format="%H" HEAD`
+
+ #default commit message uses last title if a custom one is not supplied
+ if [[ -z $commit_message ]]; then
+ commit_message="publish: $commit_title"
+ fi
+
+ #append hash to commit message unless no hash flag was found
+ if [ $append_hash = true ]; then
+ commit_message="$commit_message"$'\n\n'"generated from commit $commit_hash"
+ fi
+
+ previous_branch=`git rev-parse --abbrev-ref HEAD`
+
+ if [ ! -d "$deploy_directory" ]; then
+ echo "Deploy directory '$deploy_directory' does not exist. Aborting." >&2
+ return 1
+ fi
+
+ # must use short form of flag in ls for compatibility with macOS and BSD
+ if [[ -z `ls -A "$deploy_directory" 2> /dev/null` && -z $allow_empty ]]; then
+ echo "Deploy directory '$deploy_directory' is empty. Aborting. If you're sure you want to deploy an empty tree, use the --allow-empty / -e flag." >&2
+ return 1
+ fi
+
+ if git ls-remote --exit-code $repo "refs/heads/$deploy_branch" ; then
+ # deploy_branch exists in $repo; make sure we have the latest version
+
+ disable_expanded_output
+ git fetch --force $repo $deploy_branch:$deploy_branch
+ enable_expanded_output
+ fi
+
+ # check if deploy_branch exists locally
+ if git show-ref --verify --quiet "refs/heads/$deploy_branch"
+ then incremental_deploy
+ else initial_deploy
+ fi
+
+ restore_head
+}
+
+initial_deploy() {
+ git --work-tree "$deploy_directory" checkout --orphan $deploy_branch
+ git --work-tree "$deploy_directory" add --all
+ commit+push
+}
+
+incremental_deploy() {
+ #make deploy_branch the current branch
+ git symbolic-ref HEAD refs/heads/$deploy_branch
+ #put the previously committed contents of deploy_branch into the index
+ git --work-tree "$deploy_directory" reset --mixed --quiet
+ git --work-tree "$deploy_directory" add --all
+
+ set +o errexit
+ diff=$(git --work-tree "$deploy_directory" diff --exit-code --quiet HEAD --)$?
+ set -o errexit
+ case $diff in
+ 0) echo No changes to files in $deploy_directory. Skipping commit.;;
+ 1) commit+push;;
+ *)
+ echo git diff exited with code $diff. Aborting. Staying on branch $deploy_branch so you can debug. To switch back to main, use: git symbolic-ref HEAD refs/heads/main && git reset --mixed >&2
+ return $diff
+ ;;
+ esac
+}
+
+commit+push() {
+ set_user_id
+ git --work-tree "$deploy_directory" commit -m "$commit_message"
+
+ disable_expanded_output
+ #--quiet is important here to avoid outputting the repo URL, which may contain a secret token
+ git push --quiet $repo $deploy_branch
+ enable_expanded_output
+}
+
+#echo expanded commands as they are executed (for debugging)
+enable_expanded_output() {
+ if [ $verbose ]; then
+ set -o xtrace
+ set +o verbose
+ fi
+}
+
+#this is used to avoid outputting the repo URL, which may contain a secret token
+disable_expanded_output() {
+ if [ $verbose ]; then
+ set +o xtrace
+ set -o verbose
+ fi
+}
+
+set_user_id() {
+ if [[ -z `git config user.name` ]]; then
+ git config user.name "$default_username"
+ fi
+ if [[ -z `git config user.email` ]]; then
+ git config user.email "$default_email"
+ fi
+}
+
+restore_head() {
+ if [[ $previous_branch = "HEAD" ]]; then
+ #we weren't on any branch before, so just set HEAD back to the commit it was on
+ git update-ref --no-deref HEAD $commit_hash $deploy_branch
+ else
+ git symbolic-ref HEAD refs/heads/$previous_branch
+ fi
+
+ git reset --mixed
+}
+
+filter() {
+ sed -e "s|$repo|\$repo|g"
+}
+
+sanitize() {
+ "$@" 2> >(filter 1>&2) | filter
+}
+
+parse_args "$@"
+
+if [ "${command}" = "serve" ]; then
+ run_serve
+elif [[ "${command}" = "build" ]]; then
+ run_build
+elif [[ ${command} = "deploy" ]]; then
+ if [[ ${no_build} != true ]]; then
+ run_build
+ fi
+ main "$@"
+fi
diff --git a/source/fonts/slate.eot b/source/fonts/slate.eot
old mode 100755
new mode 100644
diff --git a/source/fonts/slate.svg b/source/fonts/slate.svg
old mode 100755
new mode 100644
diff --git a/source/fonts/slate.ttf b/source/fonts/slate.ttf
old mode 100755
new mode 100644
diff --git a/source/fonts/slate.woff b/source/fonts/slate.woff
old mode 100755
new mode 100644
diff --git a/source/fonts/slate.woff2 b/source/fonts/slate.woff2
old mode 100755
new mode 100644
diff --git a/source/images/ers_cloud_logo.png b/source/images/ers_cloud_logo.png
new file mode 100644
index 00000000000..34759cfeeda
Binary files /dev/null and b/source/images/ers_cloud_logo.png differ
diff --git a/source/images/favicon.png b/source/images/favicon.png
new file mode 100644
index 00000000000..7b0db6d968e
Binary files /dev/null and b/source/images/favicon.png differ
diff --git a/source/images/logo.png b/source/images/logo.png
index fa1f13da819..e25288943db 100644
Binary files a/source/images/logo.png and b/source/images/logo.png differ
diff --git a/source/images/logo_slate.png b/source/images/logo_slate.png
new file mode 100644
index 00000000000..68a478fae36
Binary files /dev/null and b/source/images/logo_slate.png differ
diff --git a/source/includes/_authentication.md b/source/includes/_authentication.md
new file mode 100644
index 00000000000..bc9375b294a
--- /dev/null
+++ b/source/includes/_authentication.md
@@ -0,0 +1,96 @@
+# Authentication
+
+
+Every eRS Cloud API endpoint requires an access token. If token is not passed or is invalid, API will return **401** Unauthorized error.
+
+An access token can be generated at Profile -> Security.
+
+Alternatively, OAuth flow can be used to obtain a token if access is required by third party application.
+
+##OAuth
+
+
+eRS Cloud API allows access using OAuth 2 code flow to enable integration with third party applications. OAuth 2 is an open standard for authorization that enables third party applications to obtain access of API on behalf of user who wishes to approve access.
+
+Developer (having Administrator access to eRS Cloud) are require to register an application to use OAuth. Once application is registered, it is assigned a client ID and client secret. The client secret should be kept confidential and only use when authorizing between application and eRS cloud authorization server.
+
+
+> Example : Authorization Link
+
+```shell
+https://app.eresourcescheduler.cloud/login/oauth/authorize?
+response_type=code
+&client_id=SZIZIzFXUKfwnUJW
+&redirect_uri=https://example.com/oauth/callback
+&state=f2g5h3b5
+```
+
+###1. Request User Authorization
+Give user an authorization link which redirects to eRS Cloud authorization server. If using a phone or desktop app instead of a browser, this could be achieved using some browser plugin.
+
+
+**Grant Code Request Endpoint.**
+
+https://app.eresourcescheduler.cloud/login/oauth/authorize
+
+
+**Parameters: Auth Code Request**
+
+Name | Description
+----------: | :-------
+**client_id** `string` `required` | eRS Cloud generated unique client ID which was assigned while registering application.
+**redirect_uri** `string` `required` | The callback url where user will be sent back after authorization. This value must match to redirect uri, given at the time of application registration.
+**response_type** `string` `required` | This must be set to "code" for obtaining grant code.
+**state** `string` `optional` | It is used to identify or verify origin of request. Usually it is a random string which is passed along with this request and expect the same when eRS Cloud redirects back to defined redirect uri after authorization.
+
+
+
+> Example : Access Token Request
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/login/oauth/token?\
+grant_type=authorization_code\
+&code=QbD76mCzJSMJt4fc892i\
+&client_id=SZIZIzFXUKfwnUJW\
+&client_secret=4pbxCfKa1kJB2nihfbtPLixtv6Tf4V5q\
+&redirect_uri='https://example.com/oauth/callback'" \
+-H "Content-Type:application/x-www-form-urlencoded"
+```
+
+###2. Request Access Token
+
+Once authorization is complete, eRS Cloud sends redirect back to defined `redirect_uri` with a grant code parameter "code" (and state parameter if was issued at the time of requesting grant code) set.
+
+Now this grant code can be used to fetch access token from token end point.
+
+
+**Access Token Request Endpoint.**
+
+https://app.eresourcescheduler.cloud/login/oauth/token
+
+
+**Parameters: Auth Code Request**
+
+Name | Description
+----------: | :-------
+**grant_type** `string` `required` | This must be set to "authorization_code" for access token request.
+**code** `string` `required` | The grant code which was received in step 1.
+**client_id** `string` `required` | eRS Cloud generated unique client ID which was assigned while registering application.
+**client_secret** `string` `required` | The client secret which was assigned while registering application.
+**redirect_uri** `string` `required` | The callback url where user will be sent back after authorization. This value must match to redirect uri, given at the time of application registration.
+
+
+
+_To learn more about OAuth token generation flow please read here._
+
+
+eRS Cloud expects an API token to be included in all API requests in a header that looks like the following:
+
+`Authorization: Bearer B8x5Vj1O65r6wnoV`
+
+
+
+A sample API token is included in all the example requests in this document. To test requests using your account, replace the sample access token with your actual access token.
+
+
+
diff --git a/source/includes/_booking.md b/source/includes/_booking.md
new file mode 100644
index 00000000000..106397c9246
--- /dev/null
+++ b/source/includes/_booking.md
@@ -0,0 +1,521 @@
+# Booking
+
+## Booking Object
+
+>Example Response
+
+```json
+{
+ "id": 34,
+ "resource": {
+ "name": "Andy Murray",
+ "id": 2
+ },
+ "role": {
+ "name": "Business Analyst",
+ "id": 1
+ },
+ "project": {
+ "id": 5,
+ "title": "Mars Rover"
+ },
+ "task": null,
+ "start_time": "2018-12-26T09:00:00",
+ "end_time": "2018-12-31T17:00:00",
+ "unit": 1,
+ "effort": 100.0,
+ "billing_status": 1,
+ "rate_from": 8,
+ "rate": 99.40,
+ "tags": [],
+ "created_on": "2018-09-07T04:09:45.254681Z",
+ "created_by": {
+ "name": "John doe",
+ "id": 118
+ },
+ "modified_on": "2018-11-21T06:23:02.494932Z",
+ "modified_by": {
+ "name": "John doe",
+ "id": 118
+ }
+}
+```
+
+`Booking` object represents an assignment or schedule of resource on a certain project or task for a particular time range. Resource can be booked / scheduled on a project (and task) with a defined effort and capacity along with other custom defined fields.
+
+ATTRIBUTES
+
+Following attributes are available for booking object. Booking object can also be customized to have additional attributes by an Administrator user using eRS Cloud Application. To know about attributes currently applied for booking object please check Booking Profile API.
+
+Name | Description
+ ---: | :----
+**id** `integer` | eRS Cloud generated unique identifier for the booking object.
+**resource** `object` | Resource object to which this booking belongs.
+**project** `object` | Project object for which this booking was created.
+**task** `object` | Task object defines what needs to be done. Tasks could be one of the defined tasks of booking's project object.
+**role** `object` | Role object defines which role Resource needs to perform for this booking.
+**start_time** `string` | Represents starting time of booking.
+**end_time** `string` | Represents ending time of booking.
+**effort** `float` | Effort value for this booking.
+**unit** `integer` | Represents unit of effort for this booking. Unit could be one of `Capacity %` , `Total Booking Hours` or `Full Time Equivalent`.
+**progress** `integer` | Represents percentage completion for this booking.
+**billing_status** `integer` | Represents billing status for this booking. Billing Status could be one of `Inherit from Project`, `Billable`, `Non Billable`. This field is available only when financial module is active.
+**rate_from** `integer` | Represents billing rate for this booking. Billing Rate could be one of `Inherit from Project`, `Inherit from Resource`, `Inherit from Role`, `Custom`. This field is available only when financial module is active.
+**rate** `integer` | Represents rate for this booking. Rate can only be defined when `rate_from` is given as `Custom`. This field is available only when financial module is active.
+**tags** `array of strings` | Tags are the list of strings (labels) attached to this booking object which could be used for the purpose of identification or other information.
+**created_on** `string` | Timestamp at which this booking object was created.
+**created_by** `object` | Object representing user who created this booking object.
+**modified_on** `string` | Represents latest modification timestamp.
+**modified_by** `object` | Object representing most recent user who modified this booking object.
+**timezone** `integer` | Defines timezone in which booking is created. This field is only available when scheduling plus module is on.
+**disable_parallel** `integer` | Defines if the resource or project or both can or cannot have multiple bookings at a time.
+**udf_\*** | Custom user-defined fields are used to capture additional information of booking. User defined fields can be of multiple types. Custom fields are very useful to configure booking objects to best fit requirements. In given example response, all keys starting with prefix `udf_` are user defined custom fields. Learn more
+
+## Create a Booking
+
+> **`POST v1/bookings`**
+
+
+> Example Request:
+
+```shell
+ curl -v -X POST "https://app.eresourcescheduler.cloud/rest/v1/bookings" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "resource_id": 1,
+ "project_id" : 9,
+ "start_time" : "2017-06-01T09:00",
+ "end_time": "2017-06-11T17:00",
+ "udf_progress": 70,
+ "effort": 100,
+ "unit": 1
+ }'
+```
+
+Creates a new booking object.
+
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**resource_id** `required` | ID of resource object which is being booked or scheduled.
+**project_id** `required` | ID of project object which this booking object is being created for.
+**start_time** `required` | Represents start date and time for booking object. This field accepts value in ISO 8601 format for date-time i.e. yyyy-MM-ddThh:mm:ss. The value must be snapped in 15 minutes interval, which effectively means that minutes values should be one of(00/15/30/45) and seconds value should always be 0. (if given).
+**end_time** `required` | Represents end date and time for booking object. This field accepts value in ISO 8601 format for date-time i.e. yyyy-MM-ddThh:mm:ss. The value must be snapped in 15 minutes interval, which effectively means that minutes values should be one of(00/15/30/45) and seconds value should always be 0. (if given). `end_time` must always be ahead of `start_time` by at least 15 minutes as a booking of less than 15 minutes is not allowed.
+**role_id** ⚑⚑ | ID of role object which needs to be performed for this booking. This could be ID of a role which targeted resource performs (i.e "Performing Role") or any other role (i.e. "Non-Performing-Role").
+**task_id** ⚑⚑ | ID of task object which needs to be done in this booking. This could only be ID of a task which is listed in targeted project.
+**effort** `optional` | This defines how much effort is needed to complete the task. Effort value is a floating point number which could not be less than 0 and greater than 99999999.99. If effort value is not provided system will take default value 0.
+**unit** `optional` | Integer number (1-5) representing unit in which effort is being defined. Unit value could be one of the following :
**1** for `Capacity %` : This is default unit for booking. This represents `effort` in percentage of capacity of intended resource for defined time range.
**2** for `Total Booking Hours` : This defines `effort` value in fixed hours which doesn't change upon changes in booking.
~~**3** for `Hours Per day` : This could be used where a certain no of hours per day need to be spend for a booking. For example 4 hours per day (working day).~~
**4** for `Full Time Equivalent` : Full time equivalent is calculated using FTE calendar defined in Administrator calendar settings. Capacity from FTE calendar for defined time in booking, is considered as 1 FTE.
~~**5** for `Time Per Day` : It is useful where `effort` needs to put in on a particular time of every working day i.e. 4:15 PM to 5:30 PM daily. Time portion of `start_time` argument is considered as per day start time, and Time portion of `end_time` argument is considered per day end time for this booking.~~
_**Note**: Booking units **Hours per day** and **Time per day** are no longer supported. _
+**progress** `optional` | This defines percentage completion of the booking. Progress is a integer number which could not be less than 0 and greater than 100. If progress is not provided, system will take default value 0.
+**billing_status** `optional` | Integer number (1/2/4) representing billing status of the booking. Billing status value could be one of the following :
**1** for `Inherit from Project` : This represents billing status will be the same as given for the project associated with this booking.
**2** for `Billable` : This defines billing status as billable for this booking.
**4** for `Non Billable` : This is used to set the booking to non billable.
_**Note**: Default value of billing status can be set from Administrator Scheduling Settings. This field is available only when financial module is active._ |
+**rate_from** `optional` | Integer number (1/2/4/8) representing billing rate of the booking. Billing rate value could be one of the following :
**1** for `Inherit from Project` : This represents billing rate will be the same as given for the project associated with this booking.
**2** for `Inherit from Resource` : This represents billing rate will be the same as given for the resource associated with this booking.
**4** for `Inherit from Role` : This represents billing rate will be the same as given for the performing role associated with this booking.
**8** for `Custom` : This represents custom hourly rate can be defined on this booking.
_**Note**: Default value of billing rate can be set from Administrator Scheduling Settings. This field is available only when financial module is active._ |
+**rate** `optional` | This defines hourly billing rate associated with this booking. Rate value is a floating point number which can not be less than 0 and greater than 99999999.99. Rate can only be defined when value of `rate_from` is 8, i.e `Custom`.
_**Note**: This field is available only when financial module is active._
+**tags** ⚑ | An optional array of strings which could be attached to this booking object as labels. This can be useful for the purpose of identification or other information.
+**timezone** `optional` | One timezone can be defined for a booking.
_**Note**: This field is only available when scheduling plus module is on._
+**disable_parallel** ⚑⚑ | Defines if the resource or project or both can or cannot have multiple bookings at a time. Disable Parallel could be one of the following:
**1** for `On selected resource` : This represents there will be no bookings parallel to this booking with the same resource.
**2** for `On selected project` : This represents there will be no bookings parallel to this booking with the same project.
**3** for `On selected resource or project` : This represents there will be no bookings parallel to this booking with the same resource or project.
+**udf_\*** ⚑⚑ | A user with Administrator rights can add custom fields. These fields can be used to capture additional information in Bookings. The value for user defined field can be passed as shown in example request. In given example `udf_progress` is a user defined field. Learn more
_**Note**: User with Administrator rights can make fields marked with ⚑ mandatory and remove fields marked with ⚑, from booking profile using eRS Cloud Application. If mandatory fields are not passed with a valid value or removed fields are passed while creating booking, the operation will fail with response code **400**_.
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+| **201** `Created` | This status code indicates that the operation was successful and a booking is created successfully.|
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed. Additionally, Bad request may also occur in one of these conditions :
Booking is starting before the `start_date` of resource or ending after the `last_date` of resource (if resource has a `last_date` defined.)
Resource is Archived i.e. if targeted resource has a `last_date` of past.
Project is marked as Archived.
Duration of booking is more than allowed booking duration set by Administrator using ers Cloud Application in Administrator Scheduling Settings.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+
+## List Bookings
+
+Returns list of bookings. The bookings are returned sorted by booking's `start_time` and ID.
+
+> **`GET /v1/bookings`**
+
+> Example Request
+
+```shell
+curl -v "https://app.eresourcescheduler.cloud/rest/v1/bookings?\
+start=2018-01-01&end=2018-12-31" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+>Example Request With Offset And Limit
+
+```shell
+curl -v "https://app.eresourcescheduler.cloud/rest/v1/bookings?\
+start=2018-01-01&end=2018-12-31&offset=1&limit=10" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "total_count": 7,
+ "data": [{
+ "id": 34,
+ "resource": {
+ "name": "Andy Murray",
+ "id": 2
+ },
+ "role": {
+ "name": "Business Analyst",
+ "id": 1
+ },
+ "project": {
+ "id": 5,
+ "title": "Mars Rover"
+ },
+ "task": null,
+ "start_time": "2018-12-26T09:00:00",
+ "end_time": "2018-12-31T17:00:00",
+ "unit": 1,
+ "effort": 100.0,
+ "billing_status": 1,
+ "rate_from": 8,
+ "rate": 99.40,
+ "tags": [],
+ "created_on": "2018-09-07T04:09:45.254681Z",
+ "created_by": {
+ "name": "John doe",
+ "id": 118
+ },
+ "modified_on": "2018-11-21T06:23:02.494932Z",
+ "modified_by": {
+ "name": "John doe",
+ "id": 118
+ }
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`500`**. _Maximum value of `limit` can be_ **`5000`**.
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**.
+**start** `optional` | String value representing start date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter bookings starting on or after this date.
+**end** `optional` | String value representing end date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter bookings starting before this date.
+||_**Note**: By default if `start` & `end` arguments are omitted, then bookings of current month will be returned. If bookings of a certain period are needed, then both `start` & `end` arguments required. If only one argument `start` or `end` is passed then a bad request error is raised._
+
+
+### Returns
+
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` |This indicates that the operation was successful and list of bookings is returned. |
+**400** `Bad Request` | Bad Request may occur when offset or limit value is negative integer.|
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+
+
+## Retrieve a Booking
+
+> **`GET v1/bookings/{ID}`**
+
+> Example Request
+
+```shell
+curl -v -X GET "https://app.eresourcescheduler.cloud/rest/v1/bookings/34" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "id": 34,
+ "resource": {
+ "name": "Andy Murray",
+ "id": 2
+ },
+ "role": {
+ "name": "Business Analyst",
+ "id": 1
+ },
+ "project": {
+ "id": 5,
+ "title": "Mars Rover"
+ },
+ "task": null,
+ "start_time": "2018-12-26T09:00:00",
+ "end_time": "2018-12-31T17:00:00",
+ "unit": 1,
+ "effort": 100.0,
+ "billing_status": 1,
+ "rate_from": 8,
+ "rate": 99.40,
+ "tags": [],
+ "created_on": "2018-09-07T04:09:45.254681Z",
+ "created_by": {
+ "name": "John doe",
+ "id": 118
+ },
+ "modified_on": "2018-11-21T06:23:02.494932Z",
+ "modified_by": {
+ "name": "John doe",
+ "id": 118
+ }
+}
+```
+Retrieves the details of an existing booking. You only need to provide the unique booking identifier that was returned upon booking creation.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This status code indicates that the operation was successful and a booking returned successfully.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested booking does not exist (i.e. There is no booking with given ID). This may also occur when requesting a booking that has been deleted.
+
+## Search Bookings
+
+
+
+> **`POST /v1/bookings/search`**
+
+> Example Request For Filter In JSON Format
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/bookings/search?\
+start=2018-01-01&end=2018-12-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "id": 1
+ }'
+```
+
+> Example Request For Filter By Passing Multiple Filters In JSON Format
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/bookings/search?\
+start=2018-01-01&end=2018-12-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "resource":{"id":2},
+ "project":{"id":9},
+ "role_id:eq": 1,
+ "tags:none": ["tagX","tagY"]
+ }'
+```
+
+> Example Response
+
+```json
+{
+ "total_count": 7,
+ "data": [{
+ "id": 34,
+ "resource": {
+ "name": "Andy Murray",
+ "id": 2
+ },
+ "role": {
+ "name": "Business Analyst",
+ "id": 1
+ },
+ "project": {
+ "id": 9,
+ "title": "Mangalyaan"
+ },
+ "task": null,
+ "start_time": "2018-12-26T09:00:00",
+ "end_time": "2018-12-31T17:00:00",
+ "unit": 1,
+ "effort": 100.0,
+ "billing_status": 1,
+ "rate_from": 8,
+ "rate": 99.40,
+ "tags": [],
+ "created_on": "2018-09-07T04:09:45.254681Z",
+ "created_by": {
+ "name": "John doe",
+ "id": 118
+ },
+ "modified_on": "2018-11-21T06:23:02.494932Z",
+ "modified_by": {
+ "name": "John doe",
+ "id": 118
+ }
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`500`**. _Maximum value of `limit` can be_ **`5000`**.
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**.
+**start** `optional` | String value representing start date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter bookings starting on or after this date.
+**end** `optional` | String value representing end date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter bookings starting before this date.
+||_**Note**: By default if `start` & `end` arguments are omitted, then bookings of current month will be returned. If bookings of a certain period are needed, then both `start` & `end` arguments required. If only one argument `start` or `end` is passed then a bad request error is raised._
+
+Search Booking API allows filtering the results set in various ways. This enables a great power to find out what is needed. eRS Cloud API also allows filtering on custom defined fields with multiple operators and conditions to cover up complex scenarios for searching.
+
+A filter condition consists of three components which are **_field_**, **_operator_** and **_value_**. For example, fetching only those bookings having tag `tagA` or `tagB`, could be achieved by adding `"tags:any": ["tagA", "tagB"]` to request body. If operator is not supplied, it takes default operator for field.
+
+Below is a list of available fields, which allow filtering bookings:
+
+|**Field Type** | **Operator** | **Example**|
+:--| :--- | :--- | :--- |
+**role_id**|
_**Note**: Integer number (2/4) representing billing status of the booking. Billing status value could be one of the following :
**2** for `Billable` : This defines billing status as `billable` for this booking.
**4** for `Non Billable` : This defines billing status as `non billable` for this booking.
_
+
+_Additionally, bookings can also be filtered using resource fields, project fields and custom fields of bookings. An example request for fetching only booking having `resource_id` as 2, `project_id` as 9 and `role_id` as 1 is shown._
+
+## Update a Booking
+
+Updates the specified booking by setting values of parameters passed. Values of any parameters which are not provided will be unchanged. To unset existing value for a parameter, just pass an empty value i.e. `null`.
+
+> **`PUT /v1/bookings/{ID}`**
+
+> Example Request
+
+```shell
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest/v1/bookings/34" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "resource_id": 3,
+ "project_id" : 4,
+ "start_time" : "2018-06-05T09:00",
+ "unit": 1
+ }'
+```
+
+> Example Request: Update a recurring booking and all its related bookings.
+
+```shell
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest\
+/v1/bookings/28?update_connected_bookings=1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "start_time" : "2022-12-05T09:00"
+ }'
+```
+
+> Example Request: Update a recurring booking and all its future bookings.
+
+```shell
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest\
+/v1/bookings/28?update_connected_bookings=2" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "start_time" : "2022-12-05T09:00"
+ }'
+```
+
+> Example Request: Update a recurring booking without changing related bookings.
+
+```shell
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest\
+/v1/bookings/28?update_connected_bookings=4" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "start_time" : "2022-12-05T09:00"
+ }'
+```
+
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**resource_id** `required` | ID of resource object which is being booked or scheduled. This will throw an error if you post an empty value.
+**project_id** `required` | ID of project object which this booking object is being created for. This will throw an error if you post an empty value.
+**start_time** `required` | Represents start date and time for booking object. This field accepts value in ISO 8601 format for date-time i.e. yyyy-MM-ddThh:mm:ss. The value must be snapped in 15 minutes interval, which effectively means that minutes values should be one of(00/15/30/45) and seconds value should always be 0. (if given). This will throw an error if you post an empty value.
+**end_time** `required` | Represents end date and time for booking object. This field accepts value in ISO 8601 format for date-time i.e. yyyy-MM-ddThh:mm:ss. The value must be snapped in 15 minutes interval, which effectively means that minutes values should be one of(00/15/30/45) and seconds value should always be 0. (if given). `end_time` must always be ahead of `start_time` by at least 15 minutes as a booking of less than 15 minutes is not allowed. This will throw an error if you post an empty value.
+**role_id** ⚑⚑ | ID of role object which needs to be performed for this booking. This could be ID of a role which targeted resource performs (i.e "Performing Role") or any other role (i.e. "Non-Performing-Role").
+**task_id** ⚑⚑| ID of task object which needs to be done in this booking. This could only be ID of a task which is listed in targeted project.
+**effort** `optional` | This defines how much effort is needed to complete the task. Effort value is a floating point number which could not be less than 0 and greater than 99999999.99. If effort value is not provided system will take default value 0.
+**unit** `optional` | Integer number (1-5) representing unit in which effort is being defined. Unit value could be one of the following :
**1** for `Capacity %` : This is default unit for booking. This represents `effort` in percentage of capacity of intended resource for defined time range.
**2** for `Total Booking Hours` : This defines `effort` value in fixed hours which doesn't change upon changes in booking.
~~**3** for `Hours Per day` : This could be used where a certain no of hours need to be spend for a booking. For example 4 hours per day (working day).~~
**4** for `Full Time Equivalent` : Full time equivalent is calculated using FTE calendar defined in Administrator calendar settings. Capacity from FTE calendar for defined time in booking, is considered as 1 FTE.
~~**5** for `Time Per Day` : It is useful where `effort` needs to put in on a particular time of every working day i.e. 4:15 PM to 5:30 PM daily. Time portion of `start_time` argument is considered as per day start time, and Time portion of `end_time` argument is considered per day end time for this booking.~~
_**Note**: Booking units **Hours per day** and **Time per day** are no longer supported._
+**progress** `optional` | This defines percentage completion of the booking. Progress is a integer number which could not be less than 0 and greater than 100. If progress is not provided, system will take default value 0.
+**billing_status** `optional` | Integer number (1/2/4) representing billing status of the booking. Billing Status value could be one of the following :
**1** for `Inherit from Project` : This represents billing status will be the same as given for the project associated with this booking.
**2** for `Billable` : This defines billing status as billable for this booking.
**4** for `Non Billable` : This is used to set the booking to non billable.
_**Note**: Default value of billing status can be set from Administrator Scheduling Settings. This field is available only when financial module is active._ |
+**rate_from** `optional` | Integer number (1/2/4/8) representing billing rate of the booking. Billing rate value could be one of the following :
**1** for `Inherit from Project` : This represents billing rate will be the same as given for the project associated with this booking.
**2** for `Inherit from Resource` : This represents billing rate will be the same as given for the resource associated with this booking.
**4** for `Inherit from Role` : This represents billing rate will be the same as given for the performing role associated with this booking.
**8** for `Custom` : This represents custom hourly rate can be defined on this booking.
_**Note**: Default value of billing rate can be set from Administrator Scheduling Settings. This field is available only when financial module is active._ |
+**rate** `optional` | This defines hourly billing rate associated with this booking. Rate value is a floating point number which can not be less than 0 and greater than 99999999.99. Rate can only be defined when value of `rate_from` is 8, i.e `Custom`.
_**Note**: This field is available only when financial module is active._
+**tags** ⚑ | Tags is an optional field. Tags are attached to this booking object which could be used for the purpose of identification or other information.. This may be up to 50 characters. This will be blank if you post an empty value.
+**timezone** `optional` | One timezone can be defined for a booking.
_**Note**: This field is only available when scheduling plus module is on._
+**disable_parallel** ⚑⚑ | Defines if the resource or project or both can or cannot have multiple bookings at a time. Disable Parallel could be one of the following:
**1** for `On selected resource` : This represents there will be no bookings parallel to this booking with the same resource.
**2** for `On selected project` : This represents there will be no bookings parallel to this booking with the same project.
**3** for `On selected resource or project` : This represents there will be no bookings parallel to this booking with the same resource or project.
+**udf_\*** ⚑⚑ | A user with Administrator rights can add such custom fields. These fields can be used to capture additional info in bookings. Learn more
_**Note**: User with Administrator rights can make fields marked with ⚑ mandatory and remove fields marked with ⚑, from booking profile using eRS Cloud Application. If mandatory fields are not passed with a valid value or removed fields are passed while updating booking, the operation will fail with response code **400**_.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This indicates that the operation was successful and a booking updated successfully.
+**409** `Conflict` | Conflict indicates that you are updating a recurring booking, so you must pass the parameter `update_connected_bookings` to replicate the changes to the related bookings. The value for the parameter `update_connected_bookings` can be **1**(to update all bookings), **2**(to update all future bookings) or **4**(to update only this booking) as shown in the example requests.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, empty required parameters or any unknown parameter is passed. Additionally, Bad request may also occur in one of these conditions :
Trying to update `start_time` or `end_time` such that `end_time` gets earlier than `start_time`.
Trying to update `start_time` of booking before the `start_date` of resource or `end_time` after the `last_date` of resource (if resource has a `last_date` defined.)
Trying to update a booking of archived resource
Trying to update bookings of archived project.
Duration of booking is more than allowed booking duration set by Administrator using ers Cloud Application in Administrator Scheduling Settings.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested booking does not exist (i.e. There is no booking with given ID). This may also occur when requesting a booking that has been deleted.
+
+
+
+
+## Delete a Booking
+
+Permanently deletes a booking. It cannot be undone.
+
+> **`DELETE /v1/bookings/{ID}`**
+
+
+> Example Request
+
+```shell
+curl -v -X DELETE "https://app.eresourcescheduler.cloud/rest\
+/v1/bookings/1" -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Request: Delete a recurring booking and all its related bookings.
+
+```shell
+curl -v -X DELETE "https://app.eresourcescheduler.cloud/rest\
+/v1/bookings/28?delete_connected_bookings=1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Request: Delete a recurring booking and all its future bookings.
+
+```shell
+curl -v -X DELETE "https://app.eresourcescheduler.cloud/rest\
+/v1/bookings/28?delete_connected_bookings=2" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Request: Delete a recurring booking without affecting related bookings.
+
+```shell
+curl -v -X DELETE "https://app.eresourcescheduler.cloud/rest\
+/v1/bookings/28?delete_connected_bookings=4" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+### Returns
+
+
+| Code | Description
+| ---: | :----
+**200** `OK` | This status code indicates that the operation was successful and a booking deleted successfully.
+**409** `Conflict` | Conflict indicates that you are deleting a recurring booking, so you must pass the parameter `delete_connected_bookings` to delete the related bookings. The value for the parameter `delete_connected_bookings` can be **1**(to delete all bookings), **2**(to delete all future bookings) or **4**(to delete only this booking). Kindly refer to the example requests.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested booking does not exist or has been deleted already.
diff --git a/source/includes/_bookingprofile.md b/source/includes/_bookingprofile.md
new file mode 100644
index 00000000000..2bfecaa7e23
--- /dev/null
+++ b/source/includes/_bookingprofile.md
@@ -0,0 +1,193 @@
+
+# Booking Profile
+
+## Booking Profile Object
+
+Booking profile object represents booking profile.
+
+> **`/v1/booking/fields`**
+
+> Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/booking/fields" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Response
+
+```json
+{
+ "id": 43,
+ "code": "rate_from",
+ "display_name": "Billing Rate",
+ "field_type": "RTFRM",
+ "minnum": 0,
+ "is_system_defined": true,
+ "is_required": false
+},
+{
+ "id": 42,
+ "code": "billing_status",
+ "display_name": "Billing Status",
+ "field_type": "BLSTS",
+ "minnum": 0,
+ "is_system_defined": true,
+ "is_required": false
+},
+{
+ "id": 46,
+ "code": "disable_parallel",
+ "display_name": "Disable Parallel",
+ "field_type": "DDSS",
+ "is_system_defined": true,
+ "is_required": false
+},
+{
+ "id": 29,
+ "code": "effort",
+ "display_name": "Effort",
+ "field_type": "EFFORT",
+ "minnum": 0,
+ "is_required": false,
+ "is_system_defined": true
+},
+{
+ "id": 17,
+ "code": "end_time",
+ "display_name": "Ends",
+ "field_type": "DATIM",
+ "is_required": true,
+ "is_system_defined": true
+ "maxdate": "2099-12-31",
+ "mindate": "1900-01-01"
+},
+{
+ "id": 31,
+ "code": "role_id",
+ "display_name": "Performing Role",
+ "field_type": "ROLEPS",
+ "is_required": false,
+ "is_system_defined": true
+ "options": [
+ {
+ "id": 5,
+ "name": "Architect",
+ "description": null
+ },
+ {...},
+ {...}
+ ]
+},
+{
+ "id": 44,
+ "code": "progress",
+ "display_name": "Progress",
+ "field_type": "INT",
+ "minnum": 0,
+ "maxnum": 100,
+ "is_system_defined": true,
+ "is_required": false
+},
+{
+ "id": 3,
+ "code": "project_id",
+ "display_name": "Project",
+ "field_type": "PRJSS",
+ "is_required": true,
+ "is_system_defined": true
+},
+{
+ "id": 75,
+ "code": "requirement_id",
+ "display_name": "Requirement",
+ "field_type": "REQSS",
+ "is_system_defined": true,
+ "is_required": false
+ },
+{
+ "id": 2,
+ "code": "resource_id",
+ "display_name": "Resource",
+ "field_type": "RSRSS",
+ "is_required": true,
+ "is_system_defined": true
+},
+{
+ "id": 16,
+ "code": "start_time",
+ "display_name": "Starts",
+ "field_type": "DATIM",
+ "is_required": true,
+ "is_system_defined": true
+ "maxdate": "2099-12-31",
+ "mindate": "1900-01-01"
+},
+{
+ "id": 32,
+ "code": "tags",
+ "display_name": "Tags",
+ "field_type": "TAGS",
+ "is_required": false,
+ "is_system_defined": true
+},
+{
+ "id": 30,
+ "code": "task_id",
+ "display_name": "Task",
+ "field_type": "TSKSS",
+ "is_required": false,
+ "is_system_defined": true
+},
+{
+ "id": 27,
+ "code": "timezone",
+ "display_name": "Time Zone",
+ "field_type": "DDSS",
+ "is_system_defined": true,
+ "is_required": false,
+ "options": [
+ {
+ "id": 136,
+ "name": "Africa/Abidjan",
+ "description": "Africa/Abidjan"
+ },
+ {...},
+ {...}
+ ]
+},
+{
+ "id": 5,
+ "code": "unit",
+ "display_name": "Unit",
+ "field_type": "UNIT",
+ "minnum": 1,
+ "is_required": false,
+ "is_system_defined": true
+}
+
+```
+
+
+
+ATTRIBUTES
+
+Name | Description
+| ---: | :---- |
+**id** `integer` | Represents unique identification number of this field, which can be used to refer or search it.
+**code** `string` | It represents the unique code of the field which is referred as API code. This code acts as `key` in API response and the same must be used as `key` to pass values for a POST or PUT request.
+**field_type** `string` | Represents the type of field. For example TEXT (for Text Field), INT (for Integer Number field), DDSS (for Dropdown Single Select Field), etc. See User Defined Fields to know more about different field types.
+**display_name** `string` |Name of this field to identify it.
+**is_system_defined** `boolean` | Indicates whether this field is system defined or a custom field. Fields which are system defined can not be customized.
+**is_required** `boolean` |Indicates whether this field is mandatory or not. If this field is a required field then a valid value for this field must be passed while creating such object and while updating object (if this field is intended to update).
+**regex** `string` | Represents regular expression which must be matched by value for this field. Only applicable for text fields.
+**fields.minlength** `integer` | Represents minimum no of characters in value this field can accept. Only applicable for text fields.
+**fields.maxlength** `integer` | Represents maximum no of characters in value this field can accept. Only applicable for text fields.
+**minnum** `integer` | Represents minimum value this field can accept. Only applicable for numeric fields.
+**maxnum** `integer` | Represents maximum value this field can accept. Only applicable for numeric fields.
+**mindate** `string` |Represents minimum value this field can accept. Only applicable for date / date time fields.
+**maxdate** `string` |Represents maximum value this field can accept. Only applicable for date / date time fields.
+**options** `array of objects` | Field types such as Dropdown Single Select, Dropdown Multi Select, Radio Group etc. ( See User Defined Fields to know more. ) Allows user to pick one or more from these available options.
+**options.id** `integer` | Represents unique identification number for the individual option object.
+**options.name** `string` | Represents name or content of option object.
+**options.color** `string` | Allows a user to store color code of option object. Only applicable for LABEL type fields.
\ No newline at end of file
diff --git a/source/includes/_calendars.md b/source/includes/_calendars.md
new file mode 100644
index 00000000000..baf25100ed8
--- /dev/null
+++ b/source/includes/_calendars.md
@@ -0,0 +1,261 @@
+# Calendars
+
+## Calendar Object
+
+Calendar is used to define working-timing of resources. An Administrator user can define multiple calendars using eRS Cloud application. Each calendar may have different timings defined. Timings allow breaks and multiple timing blocks. In addition to timings, user can apply holidays and exceptions (working or non-working) on calendars. A particular calendar can be applied on a set of resources and a resource can also have multiple calendars on different time periods. eRS Cloud API allows getting details of calendars.
+
+> Example Response
+
+```json
+{
+ "id": 1,
+ "name": "New York Calendar",
+ "description": null,
+ "is_default": false,
+ "timings": [{
+ "day_num": 1,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 2,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 3,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 4,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 5,
+ "start_time": 540,
+ "end_time": 1020
+ }],
+ "holidays": [{
+ "id": 1,
+ "name": "Christmas Day",
+ "description": null,
+ "date": "2018-12-25",
+ "tags": []
+ }],
+ "exceptions": [{
+ "id": 1,
+ "name": "Over Time",
+ "description": null,
+ "date": "2018-12-20",
+ "is_working_exception": true,
+ "tags": [],
+ "timings": [{
+ "start_time": 540,
+ "end_time": 1140
+ }]
+ }],
+ "created_on": "2018-08-21T10:03:08.650207+00:00",
+ "modified_on": "2018-12-03T15:09:34.697541+00:00",
+ "created_by": {
+ "id": 118,
+ "name": "John Doe"
+ },
+ "modified_by": {
+ "id": 118,
+ "name": "John Doe"
+ }
+}
+```
+
+ATTRIBUTES
+
+Name | Description
+---------: | :-----------
+**id** `integer` | Unique identifier for the object.
+**name** `string` | A meaningful name to identify this calendar object.
+**description** `string` | Description for calendar object.
+**is_default** `boolean`| Indicates whether this calendar object is used as a default calendar or not. There can only be one (which can be changed from Administrator calendar settings) default calendar at a time. Default calendar gets applied as working calendar, if calendar is not specified while creating a resource.
+**timings** `array of objects` | List of timing objects applicable for this calendar object. Timing objects (or `timing_blocks`) are used to define working capacity for each day of week.
+**timings.day_num** `integer` | Represents day of week, starting from 0 (for Sunday) to 6 (for Saturday).
+**timings.start_time** `integer` | Represents start time for this timing block in minutes (since 12 AM) i.e. for 6:00 AM, value would be 6 * 60 = 360 and for 9:00 AM it would be 9 * 60 = 540.
+**timings.end_time** `integer` | Represents end time for this timing block in minutes (since 12 AM) i.e. for 5:00 PM, value would be (12+5) * 60 = 1020.
+**holidays** `array of objects` | List of holiday objects applied for this calendar. There can be multiple holidays applied on calendar.
+**holidays.id** `integer` | Unique identifier for holiday object.
+**holidays.name** `string` | Name of holiday.
+**holidays.description** `string` | Description for this holiday object.
+**holidays.date** `string`| Represents date on which holiday occurs. This is a string value in ISO 8601 extended Date format i.e. yyyy-MM-dd.
+**holidays.tags** `array of string` | Tags are the list of strings (labels) attached to this holiday object which could be used for the purpose of identification or other information.
+**exceptions** `array of objects`| List of exception objects that are applied on calendar object. Exceptions are used to override working timing of calendar for a specified day.
+**exceptions.id** `integer` | Unique identifier for exception object.
+**exceptions.name** `string` | Name of exception object (which is to be displayed wherever referred).
+**exceptions.description** `string` | Description for exception object.
+**exceptions.date** `string` | Represents date on which exception is to be applied. This is a string value in ISO 8601 extended Date format i.e. yyyy-MM-dd.
+**exceptions.is_working_exception** `boolean` | Indicates whether this exception is working exception or non-working. A working exception is used to override timings of a working day and if applied on a non-working day, it turns it into working day. A non-working exception turns any working day into non-working.
+**exceptions.timings** `array of objects` | List of timing objects (or `timing_blocks`) for this exception. This defines working timings for this exception day. There are no timings if exception is a non-working exception.
+**exceptions.timings.start_time** `integer` | Represents start time for this timing block in minutes (since 12 AM) i.e. for 6:00 AM, value would be 6 * 60 = 360 and for 9:00 AM it would be 9 * 60 = 540.
+**exceptions.timings.end_time** `integer` | Represents end time for this timing block in minutes (since 12 AM) i.e. for 5:00 PM, value would be (12+5) * 60 = 1020.
+**exceptions.tags** `array of string` | Tags are the list of strings (labels) attached to this exception object which could be used for the purpose of identification or other information.
+**created_on** `string` | Timestamp at which calendar object was created.
+**modified_on** `string` | Describes the latest modification timestamp.
+**created_by** `object` | Describes by whom calendar object was created.|
+**modified_by** `object` | This field describes by whom last modification was done.
+
+## List Calendars
+
+
+Retrieves all available list of calendars.
+
+
+> **`GET /v1/calendars`**
+
+
+> Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/calendars" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+
+> Example Response
+
+```json
+{
+ "total_count": 4,
+ "data": [{
+ "id": 1,
+ "name": "New York Calendar",
+ "description": null,
+ "is_default": false,
+ "timings": [{
+ "day_num": 1,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 2,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 3,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 4,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 5,
+ "start_time": 540,
+ "end_time": 1020
+ }],
+ "created_on": "2018-08-21T10:03:08.650207+00:00",
+ "modified_on": "2018-12-03T15:09:34.697541+00:00",
+ "created_by": {
+ "id": 118,
+ "name": "John Doe"
+ },
+ "modified_by": {
+ "id": 118,
+ "name": "John Doe"
+ }
+ },
+ { ... },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+
+### Returns
+
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | Indicates that the operation was successful and list of calendars has been returned successfully. |
+
+
+
+
+## Retrieve a Calendar
+
+Retrieves the specified calendar along with exceptions and holidays applied on it.
+
+
+> **`GET /v1/calendars/{ID}`**
+
+> Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/calendars/1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "id": 1,
+ "name": "New York Calendar",
+ "description": null,
+ "is_default": false,
+ "timings": [{
+ "day_num": 1,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 2,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 3,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 4,
+ "start_time": 540,
+ "end_time": 1020
+ }, {
+ "day_num": 5,
+ "start_time": 540,
+ "end_time": 1020
+ }],
+ "holidays": [{
+ "id": 1,
+ "name": "Christmas Day",
+ "description": null,
+ "date": "2018-12-25",
+ "tags": []
+ }],
+ "exceptions": [{
+ "id": 1,
+ "name": "Over Time",
+ "description": null,
+ "date": "2018-12-20",
+ "is_working_exception": true,
+ "tags": [],
+ "timings": [{
+ "start_time": 540,
+ "end_time": 1140
+ }]
+ }],
+ "created_on": "2018-08-21T10:03:08.650207+00:00",
+ "modified_on": "2018-12-03T15:09:34.697541+00:00",
+ "created_by": {
+ "id": 118,
+ "name": "John Doe"
+ },
+ "modified_by": {
+ "id": 118,
+ "name": "John Doe"
+ }
+}
+```
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | Indicates that the operation was successful and requested calendar has been returned successfully.
+| **404** `Not Found` | indicates that calendar object with specified calendar ID does not exist or has been deleted already.
\ No newline at end of file
diff --git a/source/includes/_errors.md b/source/includes/_errors.md
index 56cffb34d22..795d4def400 100644
--- a/source/includes/_errors.md
+++ b/source/includes/_errors.md
@@ -1,20 +1,20 @@
-# Errors
+# Response Codes
-
+eRS Cloud uses conventional HTTP response codes to indicate the success or failure of an API request. In general: Codes in the 2xx range indicate success. Codes in the 4xx range indicate an error that failed due to incorrect request. (e.g., a required parameter was omitted, syntactically incorrect request, etc.). Codes in the 5xx range indicate an error with eRS Cloud's servers (which is rare).
-The Kittn API uses the following error codes:
-Error Code | Meaning
----------- | -------
-400 | Bad Request -- Your request sucks
-401 | Unauthorized -- Your API key is wrong
-403 | Forbidden -- The kitten requested is hidden for administrators only
-404 | Not Found -- The specified kitten could not be found
-405 | Method Not Allowed -- You tried to access a kitten with an invalid method
-406 | Not Acceptable -- You requested a format that isn't json
-410 | Gone -- The kitten requested has been removed from our servers
-418 | I'm a teapot
-429 | Too Many Requests -- You're requesting too many kittens! Slow down!
-500 | Internal Server Error -- We had a problem with our server. Try again later.
-503 | Service Unavailable -- We're temporarially offline for maintanance. Please try again later.
+### List of Status Codes :
+
+Status Code | Meaning
+----------: | :-------
+**200** **`OK`** | Everything worked as expected.
+**201** **`Created`** | This indicates successful creation of intended object.
+**400** **`Bad Request`** | Indicates that request is not acceptable, often due to missing required parameters or invalid value for any parameter.
+**401** **`Unauthorized`** | No valid API access token provide. Authentication failed due to invalid authentication credentials.
+**403** **`Forbidden`** | Accessing an object or performing an action when user doesn't have required permissions, causes this error.
+**404** **`Not Found`** | The requested resource doesn't exist.
+**405** **`Method Not Allowed`** | HTTP method is not allowed by a web server for a requested URL.
+**409** **`Conflict`** | Occurs when trying to create a duplicate object where duplicates are not allowed or when request could affect other objects.
+**415** **`Unsupported Media Type`** | No valid media is provided.
+**500** **`Internal Server Error`** | Something went wrong at eRS Cloud's end. _(This is rare.)_
\ No newline at end of file
diff --git a/source/includes/_filter.md b/source/includes/_filter.md
new file mode 100644
index 00000000000..b73559e1c94
--- /dev/null
+++ b/source/includes/_filter.md
@@ -0,0 +1,47 @@
+# Filters
+
+## Definition
+
+The filter parameter allows for filtering the results returned from the various endpoint in various ways.
+
+Filters are made up of rules, with a user-defined or system-defined field, a filter operator and a value.
+
+A filter condition consists of three components which are **_field_**, **_operator_** and **_value_**. If operator is not supplied, it takes default operator for field.
+
+## Operator
+
+The full list of all operators is shown below.
+
+
+| Operator | Meaning
+| -: |:- |
+| any | Checks whether field value exists in given set. |
+| all | Checks whether field value contains all elements of given set. |
+| has | Checks whether field value contains given phrase. |
+| eq | Checks whether field value is equal to given input. |
+| gt | Checks whether field value is greater than given input. |
+| lt | Checks whether field value is lesser than given input. |
+| bt | Checks whether field value is between given range. |
+| ex | Checks whether field value is not in the given range. |
+| none | Checks whether field value does not exist in given set. |
+| miss | Checks whether field value does not contain given phrase. |
+| neq | Checks whether field value is not equal to given input. |
+
+## Filters for User Defined Fields
+
+|**Field Type**| **Operators** | **Example**|
+|:--|:--|:--|
+|**Simple Text**|
**has** *(default)*
miss
eq
neq
|`"simtext:has": "Simple Text"` `"simtext:miss": "Simple Text"` `"simtext:eq": "Simple Text Ed"` `"simtext:neq": "Simple Text Ed"`
+|**Integer Number**|
|`"ums_field:any":[20,21]` `"ums_field:none": [20,21]` `"ums_field:all": [20,21]` `"ums_field:ex": [20,21]`
\ No newline at end of file
diff --git a/source/includes/_introduction.md b/source/includes/_introduction.md
new file mode 100644
index 00000000000..79523dbb941
--- /dev/null
+++ b/source/includes/_introduction.md
@@ -0,0 +1,26 @@
+# Introduction
+
+## API Reference
+
+
+
+>Base URL
+
+
+```shell
+ https://app.eresourcescheduler.cloud/rest
+
+```
+>Note: If you are using self-hosted version, the base URL will be
+
+```shell
+ https://yourowndomain/rest
+
+```
+
+eRS Cloud API is organized around Rest. Our API has predictable, resource-oriented URLs, and uses HTTP response codes to indicate API errors.
+We support cross-origin resource sharing, allowing you to interact securely with our API from a web application (though you should never expose your secret API key). JSON will be returned by all API responses including errors. Use our API to access eRS Cloud API end-points, which can get you information of resources, projects, bookings and timesheets in our database.
\ No newline at end of file
diff --git a/source/includes/_project.md b/source/includes/_project.md
new file mode 100644
index 00000000000..8d59d5abc33
--- /dev/null
+++ b/source/includes/_project.md
@@ -0,0 +1,1462 @@
+# Project
+
+## Project Object
+>Example Response
+
+```json
+ {
+ "id": 1,
+ "title": "Project-A",
+ "type": {
+ "name": "Satellite",
+ "description": null,
+ "id": 1
+ },
+ "email": "apollo@enbraun.com",
+ "project_start_date": null,
+ "end_date": null,
+ "image": "https://erscloud/img/7aca31f5-29ae205ba315",
+ "tags": ["NASA"],
+ "timezone": {
+ "name": "(UTC-10:00) Pacific/Honolulu (HST)",
+ "description": "Pacific/Honolulu",
+ "id": 316
+ },
+ "disable_parallel_booking": false,
+ "is_archive": false,
+ "created_on": "2018-08-20T09:25:34.925474Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2018-09-28T12:32:44.896426Z",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "udf_color": "#FF8A80;0",
+ "udf_progress": 70,
+ "udf_project_manager": "Gene Kranz",
+ "udf_priority": {
+ "name": "High",
+ "description": null,
+ "id": 21
+ }
+ }
+```
+
+`Project` object contains all the information about a project. Project is used as an activity for resources to be scheduled for. The API allows you to list, search, create, delete, and update project.
+
+ATTRIBUTES
+
+Name | Description
+ ---: | :----
+**id** `integer` | eRS Cloud generated unique identifier for the project object.
+**title** `string` | Represents title or name of the project. It can be up to 255 characters.
+**type** `object` | Describes the type of project. This is one of the project type objects which an Administrator user creates using eRS Cloud Application.
+**email** `string` | An optional email address of project object.
+**project_start_date** `string` | Date on which project is considered started.
+**end_date** `string` | Date on which project is considered ended / completed.
+**image** `string` | String value representing URL of image file of project.
+**tags** `array of strings` | Tags are the list of strings (labels) attached to this project object which could be used for the purpose of filtering, identification or other information.
+**timezone** `integer` | Defines and categorize projects based on their location. This field is only available when scheduling plus module is on.
+**project_calendar** `integer` | ID of the Calendar object, which should be assigned to the project. Depending upon requirements, different calendars can be applied to different projects. If the calendar is omitted, then the default calendar (as defined in the Administrator calendar settings) will be applied to this project.This field is only available when scheduling plus module is on.
+**is_archive** `boolean` | Boolean value representing whether this project is archived or not.
+**created_on** `string` | Timestamp at which this project object was created.
+**created_by** `object` | Object representing user who created this project object.
+**modified_on** `string` | Represents latest modification timestamp.
+**disable_parallel_booking** `boolean` | Boolean value defining if project can or cannot have multiple bookings at a time. Default value for disable parallel booking is false.
+**modified_by** `object` | Object representing most recent user who modified this project object.
+**udf_\*** | Custom user-defined fields used to capture additional information of project. User defined field can be of multiple types. Custom fields are very useful to configure project objects to best fit requirements. In given example response, all keys starting with prefix `udf_` are user defined custom fields. Learn more
+
+## Create a Project
+
+Creates a new project object.
+
+> **`POST /v1/projects`**
+
+> Example Request:
+
+```shell
+ curl -v -X POST "https://app.eresourcescheduler.cloud/rest/v1/projects" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "title": "Project-A",
+ "project_type_id": 1,
+ "project_start_date": "2016-05-02",
+ "email": "andrew@enbraun.com",
+ "udf_confirmed": true
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+ **project_type_id** `required` | ID of project-type object. A project must be linked with one of project-type defined in Administration section (_using eRS Cloud Application_). Let’s assume there are two project types defined as `Medical` (_having ID as 1_) and `Education` (_having ID as 2_), now while creating a new project, if `project_type_id` is given as **1** then it will get created under Medical type and the same for Education when `project_type_id` is given as **2**.
+**title** `required` | String representing title / name of project. This can be a maximum of 255 characters long.
+**email** ⚑⚑ | String value representing email address of project object. Email address must be properly formatted with a maximum length of 254 characters.
+**project_start_date** ⚑⚑ | String value representing a date in ISO 8601 extended notation for date i.e. yyyy-MM-dd.
+**end_date** ⚑⚑ | String value representing a date in ISO 8601 extended notation for date i.e. yyyy-MM-dd.
+**tags** ⚑ | An optional array of strings which could be attached to this project object as labels. This can be useful for the purpose of filtering, identification or other information.
+**timezone** ⚑⚑ | One timezone object can be defined for a project.
_**Note**: This field is only available when scheduling plus module is on._
+**project_calendar** | ID of the Calendar object, which should be assigned to the project. Depending upon requirements, different calendars can be applied to different projects. If the calendar is omitted, then the default calendar (as defined in the Administrator calendar settings) will be applied to this project.
_**Note**: This field is only available when scheduling plus module is on._
+**disable_parallel_booking** `optional` | Boolean value defining if project can or cannot have multiple bookings at a time. Default value for disable parallel booking is false.
+**udf_\*** ⚑⚑ | A user with Administrator rights can add custom fields. These fields can be used to capture additional information in Projects. Different types of projects may have a different set of user-defined fields. The value for user defined field can be passed as shown in example request. In given example `udf_confirmed` is a user defined field. Learn more
_**Note**: User with Administrator rights can make fields marked with ⚑ mandatory and remove fields marked with ⚑, from specific project type using eRS Cloud Application. If mandatory fields are not passed with a valid value or removed fields are passed while creating project, the operation will fail with response code **400**_.
+
+### Returns
+
+| Code | Description |
+| :--- | :---- |
+**201** `Created` | Indicates that the operation was successful and a project created successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or has any unknown parameter.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+
+
+## List Projects
+
+
+Returns a list of projects. The projects are returned sorted by `title`.
+
+
+> **`GET /v1/projects`**
+
+
+> Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/projects" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+
+>Example Request With Offset And Limit
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/projects?offset=1&limit=15" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "total_count": 50,
+ "offset": 1,
+ "limit": 15,
+ "data": [{
+ "id": 1,
+ "title": "Project-A",
+ "type": {
+ "name": "Satellite",
+ "description": null,
+ "id": 1
+ },
+ "email": "apollo@enbraun.com",
+ "project_start_date": null,
+ "end_date": null,
+ "image": "https://erscloud/img/7aca31f5-29ae205ba315",
+ "tags": ["NASA"],
+ "timezone": {
+ "name": "(UTC-10:00) Pacific/Honolulu (HST)",
+ "description": "Pacific/Honolulu",
+ "id": 316
+ },
+ "disable_parallel_booking": false,
+ "is_archive": false,
+ "created_on": "2018-08-20T09:25:34.925474Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2018-09-28T12:32:44.896426Z",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "udf_color": "#FF8A80;0",
+ "udf_progress": 70,
+ "udf_project_manager": "Gene Kranz",
+ "udf_priority": {
+ "name": "High",
+ "description": null,
+ "id": 21
+ }
+ },
+ { ... },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`25`**. _Maximum value of `limit` can be_ **`500`**.
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**.
+
+
+### Returns
+
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and list of projects is returned.
+**400** `Bad Request` | Bad Request may occur when offset or limit value is negative.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+
+## Retrieve a Project
+
+
+> **`GET /v1/projects/{ID}`**
+
+> Example Request
+
+```shell
+curl -v "https://app.eresourcescheduler.cloud/rest/v1/projects/1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "id": 1,
+ "title": "Project-A",
+ "type": {
+ "name": "Satellite",
+ "description": null,
+ "id": 1
+ },
+ "email": "apollo@enbraun.com",
+ "project_start_date": null,
+ "end_date": null,
+ "image": "https://erscloud/img/7aca31f5-29ae205ba315",
+ "tags": ["NASA"],
+ "timezone": {
+ "name": "(UTC-10:00) Pacific/Honolulu (HST)",
+ "description": "Pacific/Honolulu",
+ "id": 316
+ },
+ "project_calendar": {
+ "name": "Default",
+ "id": 1
+ },
+ "disable_parallel_booking": false,
+ "is_archive": false,
+ "created_on": "2018-08-20T09:25:34.925474Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2018-09-28T12:32:44.896426Z",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "udf_color": "#FF8A80;0",
+ "udf_progress": 70,
+ "udf_project_manager": "Gene Kranz",
+ "udf_priority": {
+ "name": "High",
+ "description": null,
+ "id": 21
+ }
+}
+```
+
+Retrieves the details of an existing project. You only need to provide the unique project identifier that was returned upon project creation as request parameter.
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This status code indicates that the operation was successful and project retrieved successfully. |
+| **403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | Not Found error occurs when requested project does not exist (i.e. There is no project with given ID). This may also occur when requesting a project that has been deleted. |
+
+## Search Projects
+> **`POST /v1/projects/search`**
+
+> Example Request For Filter In JSON Format
+
+```shell
+curl -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/search?offset=1&limit=15" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "project_type_id:eq": 1
+ }'
+```
+
+> Example Request For Filter By Passing Multiple Rules In JSON Format
+
+```shell
+curl -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/search" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "project_type_id:eq": 1,
+ "project_start_date:gt": "2015-04-02",
+ "title:miss": "z"
+ }'
+```
+
+> Example Response
+
+```json
+{
+ "total_count": 50,
+ "offset": 1,
+ "limit": 15,
+ "data": [{
+ "id": 1,
+ "title": "Project-A",
+ "type": {
+ "name": "Satellite",
+ "description": null,
+ "id": 1
+ },
+ "email": "apollo@enbraun.com",
+ "project_start_date": null,
+ "end_date": null,
+ "image": "https://erscloud/img/7aca31f5-29ae205ba315",
+ "tags": ["NASA"],
+ "disable_parallel_booking": false,
+ "is_archive": false,
+ "created_on": "2018-08-20T09:25:34.925474Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2018-09-28T12:32:44.896426Z",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "udf_color": "#FF8A80;0",
+ "udf_progress": 70,
+ "udf_project_manager": "Gene Kranz",
+ "udf_priority": {
+ "name": "High",
+ "description": null,
+ "id": 21
+ }
+ },
+ { ... },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`25`**. _Maximum value of `limit` can be_ **`500`**.
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**.
+
+
+Search Project API allows filtering the results returned in various ways. This enables a great power to find out what is needed. eRS Cloud API also allows filtering on custom defined fields with multiple operators and conditions to cover up complex scenarios for searching.
+
+A filter condition consists of three components which are **_field_**, **_operator_** and **_value_**. For example fetching only those projects having `project_type_id` 1, could be achieved by adding `"project_type_id:eq":1 ` to your query. If operator is not supplied, it takes default operator for field. Read more
+
+Below is a list of available fields, which allow filtering projects:
+
+### Filters for System-defined fields
+
+|**Field Code**| **Operator** | **Example**|
+|:--|:---|:--|
+**project_type_id**|
| `"modified_on:eq": ["2021-07-08T00:00:00]` `"modified_on:lt": ["2021-07-08T00:00:00]` `"modified_on:gt": ["2021-07-08T59:59:59"]` `"modified_on:bt": ["2021-07-08T00:00:00", "2021-07-10T23:59:59"]` `"modified_on:bt": ["2021-07-08T00:00:00", ""]` `"modified_on:bt": ["", "2021-07-10T23:59:59"]` `"modified_on:ex": ["2021-07-08T00:00:00", "2021-07-10T23:59:59"]` `"modified_on:ex": ["2021-07-08T00:00:00", ""]` `"modified_on:ex": ["", "2021-07-10T23:59:59"]]`
+_For filtering using custom fields and operators please check here._
+
+## Update a Project
+
+Updates specified project by setting the values of the parameters passed. Any parameters which are not provided remains unchanged. To unset existing value for a parameter, just pass an empty value i.e. `null`.
+
+This request accepts mostly the same arguments as `Create Project` API, except user can never update `project_type_id` of any project.
+
+> **`PUT /v1/projects/{ID}`**
+
+> Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "title": "Angola",
+ "udf_progress": 70
+ }'
+```
+
+
+REQUEST BODY PARAMETERS
+
+|Name | Description |
+| ---: | :---- |
+**title** `required` |String representing the title of a project. It can be up to 255 characters.
+**project_start_date** ⚑⚑ | String value representing a date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. The project is started from this date.
+**end_date** ⚑⚑ | String value representing a date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. The project is considered ended / completed on this date.
+**email** ⚑⚑ | String value representing email address associated with project object. Email address must be properly formatted with a maximum length of 254 characters.
+**tags** ⚑ | An optional array of strings which could be attached to this project object as labels. This can be useful for the purpose of filtering, identification or other information. It can be up to 50 characters.
+**timezone** ⚑⚑ | One timezone object can be defined for a project.
_**Note**: This field is only available when scheduling plus module is on._
+**project_calendar** | ID of the Calendar object, which should be assigned to the project. Depending upon requirements, different calendars can be applied to different projects. If the calendar is omitted, then the default calendar (as defined in the Administrator calendar settings) will be applied to this project.
_**Note**: This field is only available when scheduling plus module is on._
+**disable_parallel_booking** `optional` | Boolean value defining if project can or cannot have multiple bookings at a time. Default value for disable parallel booking is false.
+**udf_\*** ⚑⚑ | A user with Administrator rights can add custom fields. These fields can be used to capture additional information in Project. Different types of projects may have a different set of user-defined fields. The value for user defined field can be passed as shown in example request. In first example `udf_progress` is a user defined field. Learn more
_**Note**: User with Administrator rights can make fields marked with ⚑ mandatory and remove fields marked with ⚑, from specific project type using eRS Cloud Application. If mandatory fields are not passed with a valid value or removed fields are passed while updating project, the operation will fail with response code **400**_.
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and project is updated successfully.
+**400** `Bad Request` | Bad Request occurs when a request is not well-formed, syntactically incorrect, empty required parameters or any unknown parameter is passed. Additionally, Bad request may also occur when :
User tries to update archived project.
User tries to update `project_start_date` or `end_date` or both such that `end_date` gets earlier than `project_start_date`.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** Delete a Project `Not Found` | This status code indicates that project does not exist.
+
+
+## Delete a Project
+
+ Permanently deletes requested project. It cannot be undone. By default, this operation will fail if a project has any bookings, rates, timesheets or requirements associated with it. To override this, forceful deletion can be used which will delete all bookings, rates, timesheets and requirements and then, ultimately deletes the project object.
+
+> **`DELETE /v1/projects/{ID}`**
+
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Request For Forceful Delete
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/1?\
+force_delete_bookings=true&force_delete_rates=true&\
+force_delete_timesheet_entry=true&force_delete_requirements=true" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+### Returns
+
+
+| Code | Description
+| ---: | :----
+**200** `OK` |This status code indicates that the operation was successful and project deleted successfully.
+**409** `Conflict` |Conflict indicates that the project can not be deleted because there are bookings, rates, timesheets or requirements associated with this project. If you wish to delete it any way you must use force delete option by passing `true` for parameter `force_delete_bookings`, `force_delete_rates`, `force_delete_timesheet_entry` and `force_delete_requirements` which will delete all associated bookings, rates,timesheets and requirements corresponding to the project. This operation deletes all bookings, timesheets and rates of requested project and project itself (shown in example request).
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` |This status code indicates that requested project does not exist.| |
+
+## Tasks
+
+A task is a single unit of work – an action to accomplish in a project, a single step in a multi-step project. Each project has it's own set of tasks.
+
+This API allows you to list, create, delete and update tasks of any project.
+
+### List Tasks
+
+Retrieves list of all the tasks of specified project. List of tasks is returned sorted by name.
+
+>**`GET /v1/projects/{ID}/tasks`**
+
+> Example Request
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/2/tasks" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Response
+
+ ```json
+{
+ "total_count": 8,
+ "data": [{
+ "id": 9,
+ "name": "TASK- 2A",
+ "start_time": "2018-09-16T18:30:00+00:00",
+ "end_time": "2018-09-20T18:30:00+00:00",
+ "project_id": 2,
+ "created_on": "2018-09-06T10:09:00.853477+00:00",
+ "modified_on": "2018-09-27T12:32:00.853477+00:00",
+ "created_by": {
+ "id": 118,
+ "name": "John Doe"
+ },
+ "modified_by": {
+ "id": 118,
+ "name": "John Doe"
+ }
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+ATTRIBUTES
+
+
+Name | Description
+ ---: | :----
+ **ID** `integer`| Auto generated unique identifier for task object.
+ **name** `string`| Name of task object.
+**start_time** `string`| Represents start time of task object.
+**end_time** `string`| Represents end time of task object.
+**project_id** `integer` | Unique ID of project object, which this task belongs to.
+**created_on** `string` | Timestamp at which this task object was created.
+**created_by** `object` | Object representing user who created this task object.
+**modified_on** `string` | Represents latest modification timestamp.
+**modified_by** `object` | Object representing most recent user who modified this task object.
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This status code indicates that the operation was successful and list of tasks retrieved successfully.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested project task does not exist (i.e. There is no project task exists with given ID). This may also occur when requesting tasks of project that has been deleted.
+
+
+
+### Create a task
+
+Creates a new task object for specified project.
+
+
+>**`POST /v1/projects/{ID}/tasks`**
+
+>Example Request
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/2/tasks" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "name": "TASK- 2A",
+ "start_time": "2018-09-16T18:30:00Z",
+ "end_time": "2018-09-20T18:30:00Z"
+ }'
+
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+---: | :----
+**name** `required` | String representing the name of task. It can be up to 100 characters long.
+**start_time** `optional`| String representing timestamp value for start time of task. This field takes input in ISO 8601 extended notation for date and time value i.e. yyyy-MM-ddTHH:mm:ssZ and supports time zone offset as well.
+**end_time** `optional`| String representing timestamp value for end time of task. This field takes input in ISO 8601 extended notation for date and time value i.e. yyyy-MM-ddTHH:mm:ssZ and supports time zone offset as well.
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+**201** `Created` | Indicates that the operation was successful and task is created successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed. Additionally, Bad request may also occur when `start_time` is given later then `end_time`.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+
+### Update a task
+
+>**`PUT /v1/projects/{ID}/tasks/{Task_ID}`**
+
+Updates an existing task by setting the values of the parameters passed. Any parameters not passed will be left unchanged.
+
+This request accepts mostly the same arguments as the task creation call.
+
+>Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/8/tasks/9" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "name": "TASK- 2B"
+ }'
+
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**name** `required` | String representing the name of task. It can be up to 100 characters long.
+**start_time** `optional`| String representing timestamp value for start time of task. This field takes input in ISO 8601 extended notation for date and time value i.e. yyyy-MM-ddTHH:mm:ssZ and supports time zone offset as well.
+**end_time** `optional`| String representing timestamp value for end time of task. This field takes input in ISO 8601 extended notation for date and time value i.e. yyyy-MM-ddTHH:mm:ssZ and supports time zone offset as well.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and task is updated successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed. Additionally, Bad request may also occur if `start_time` becomes later then `end_time`.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that project or task does not exist.
+
+
+
+### Delete a task
+
+> **`DELETE /v1/projects/{ID}/tasks/{Task_ID}`**
+
+Permanently deletes a task. It cannot be undone. By default, this operation will fail if a task has any bookings, timesheets or requirements associated with it. To override this behavior, forceful removal can be used which will remove this task from all bookings, timesheets and requirements associated with it.
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/1/tasks/2" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Request For Forceful Delete
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/1/tasks/2\
+?remove_from_bookings=true&remove_from_timesheet=true&\
+remove_from_requirement=true"\
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+### Returns
+
+| Code | Description
+| :--- | :----
+**200** `OK` | Indicates that the operation was successful and task is deleted successfully.
+**409** `Conflict` | Conflict indicates that the task can not be deleted because there are bookings ,timesheets or requirements associated with this task. If you wish to delete it any way you must use force delete option by passing `true` for parameters `remove_from_bookings`, `remove_from_timesheet` and `remove_from_requirement`. This operation removes task from all associated bookings,timesheets and requirements, and then deletes the task itself. Example request is shown to right.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This indicates that project or task does not exist.
+
+## Phases
+
+A phase is a time frame for a project, making it easy to visualize different stages of a project. Each project has its own set of phases.
+
+This API allows you to list, create, delete and update phases of any project.
+
+### List Phases
+
+Retrieves a list of all the phases of specified project. The list of phases is returned sorted by name.
+
+>**`GET /v1/projects/{ID}/phases`**
+
+> Example Request
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/477/phases" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Response
+
+ ```json
+{
+ "total_count": 8,
+ "data": [{
+ "id": 1,
+ "name": "Documentation",
+ "description": "Product synopsis and documentation",
+ "start_date": "2022-01-04",
+ "end_date": "2022-01-11",
+ "project_id": 477,
+ "created_on": "2022-01-01T09:07:23.456852+00:00",
+ "modified_on": "2022-01-01T09:07:56.216114+00:00",
+ "created_by":{
+ "id": 1146,
+ "name": "John Smith"
+ },
+ "modified_by":{
+ "id": 1146,
+ "name": "John Smith"
+ }
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+ATTRIBUTES
+
+
+Name | Description
+ ---: | :----
+**ID** `integer`| Auto generated unique identifier for phase object.
+**name** `string` | Name of phase object.
+**description** `string` | Any other information regarding this phase.
+**start_date** `string`| Represents start date of the phase object.
+**end_date** `string`| Represents end date of the phase object.
+**project_id** `integer` | Unique ID of project object, which this phase belongs to.
+**created_on** `string` | Timestamp at which this phase object was created.
+**created_by** `object` | Object representing user who created this phase object.
+**modified_on** `string` | Represents latest modification timestamp.
+**modified_by** `object` | Object representing most recent user who modified this phase object.
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This status code indicates that the operation was successful and the phases list was successfully retrieved.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when the user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested project does not exist.
+
+
+### Create a phase
+
+Creates a new phase object for the specified project.
+
+
+>**`POST /v1/projects/{ID}/phases`**
+
+>Example Request
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/477/phases" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "name": "Development",
+ "start_date": "2022-01-14",
+ "end_date": "2022-03-27",
+ "description": "First phase of development"
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+---: | :----
+**name** `required` | String representing the name of phase. It can be up to 100 characters long.
+**start_date** `required` | String representing date value for start date of phase. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+**end_date** `required`| String representing date value for end date of phase. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+**description** `optional` | String consisting information related to this phase. It can be up to 255 characters long.
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+**201** `Created` | Indicates that the operation was successful and phase is created successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed. Additionally, a Bad Request error may also occur when `start_date` is given later than `end_date` or the date range for this phase is overlapping with any existing phase.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when the user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+
+### Update a phase
+
+>**`PUT /v1/projects/{ID}/phases/{Phase_ID}`**
+
+Updates an existing phase by setting the values of the parameters passed. Any parameters not passed will be left unchanged.
+
+This request accepts mostly the same arguments as the phase creation call.
+
+>Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/477/phases/2" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "description": "First phase of development"
+ }'
+
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**name** `required` | String representing the name of phase. It can be up to 100 characters long.
+**start_date** `required` | String representing date value for start date of phase. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+**end_date** `required`| String representing date value for end date of phase. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+**description** `optional` | String consisting information related to this phase. It can be up to 255 characters long.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and phase is updated successfully.
+**400** `Bad Request` | Bad Request occurs when a request is malformed, syntactically incorrect, empty required parameters or any unknown parameter is passed. Additionally, a Bad Request error may also occur when `start_date` is given later than `end_date` or the date range for this phase is overlapping with any existing phase.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when the user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that the project or phase does not exist.
+
+
+
+### Delete a phase
+
+> **`DELETE /v1/projects/{ID}/phases/{Phase_ID}`**
+
+Permanently deletes a phase. It cannot be undone.
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/477/phases/2" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+
+### Returns
+
+| Code | Description
+| :--- | :----
+**200** `OK` | Indicates that the operation was successful and phase is deleted successfully.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when the user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This indicates that the project or phase does not exist.
+
+
+## Milestones
+
+A milestone is a notation used to define a goal reached in a project. Each project has its own milestones.
+
+This API allows you to list, create, delete and update milestones of any project.
+
+### List Milestones
+
+Retrieves a list of all the milestones of specified project. The list of milestones is returned sorted by name.
+
+>**`GET /v1/projects/{ID}/milestones`**
+
+> Example Request
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/477/milestones" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Response
+
+ ```json
+{
+ "total_count": 4,
+ "data": [{
+ "id": 1,
+ "name": "Documentation Complete",
+ "description": "Done with initial planning & documentation.",
+ "date": "2022-01-11",
+ "color": "#3F51B5",
+ "project_id": 477,
+ "created_on": "2022-01-01T09:11:35.40366+00:00",
+ "modified_on": "2022-01-01T09:15:35.40366+00:00",
+ "created_by":{
+ "id": 1146,
+ "name": "John Smith"
+ },
+ "modified_by":{
+ "id": 1146,
+ "name": "John Smith"
+ }
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+ATTRIBUTES
+
+
+Name | Description
+ ---: | :----
+**ID** `integer` | Auto-generated unique identifier for milestone object.
+**project_id** `integer` | Unique ID of project object, which this milestone belongs to.
+**name** `string` | Name of milestone object.
+**description** `string` | Any information regarding this milestone.
+**date** `string`| Represents date of the milestone object.
+**color** `string`| String representing hexadecimal color code assigned to the milestone.
+**created_on** `string` | Timestamp at which this milestone object was created.
+**created_by** `object` | Object representing user who created this milestone object.
+**modified_on** `string` | Represents latest modification timestamp.
+**modified_by** `object` | Object representing most recent user who modified this milestone object.
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This code indicates that the operation was successful and the milestones list was retrieved successfully.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when the user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested project does not exist.
+
+
+### Create a milestone
+
+Creates a new milestone object for the specified project.
+
+
+>**`POST /v1/projects/{ID}/milestones`**
+
+>Example Request
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/477/milestones" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "name": "Development Phase 1 Completed",
+ "date": "2022-04-02",
+ "color": "#3F51B5",
+ "description": "Development phase-I is completed, staging link at https://mydomain.tld/phase1."
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+---: | :----
+**name** `required` | String representing the name of a milestone. It can be up to 100 characters long.
+**date** `required` | String representing date value for date of milestone. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+**color** `optional`| String representing a color code for this milestone object. This is helpful to visually identify a milestone on the scheduling chart.This field takes input in string format of hexadecimal color code.
+**description** `optional` | String consisting information related to this milestone. It can be up to 255 characters long.
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+**201** `Created` | Indicates that the operation was successful and a milestone is created successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when the user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that the project on which the milestone is being created, does not exist.
+
+### Update a milestone
+
+>**`PUT /v1/projects/{ID}/milestones/{Milestone_ID}`**
+
+Updates an existing milestone by setting the values of the parameters passed. Any parameters not passed will be left unchanged.
+
+This request accepts mostly the same arguments as the milestone creation call.
+
+>Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/477/milestones/1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "name": "Documentation Completed"
+ }'
+
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**name** `required` | String representing the name of a milestone. It can be up to 100 characters long.
+**date** `required` | String representing date value for date of milestone. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+**color** `optional`| String representing a color code for this milestone object. This is helpful to visually identify a milestone on the scheduling chart.This field takes input in string format of hexadecimal color code.
+**description** `optional` | String consisting information related to this milestone. It can be up to 255 characters long.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and milestone is updated successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, empty required parameters or any unknown parameter is passed.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when the user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that the project or milestone does not exist.
+
+
+
+### Delete a milestone
+
+> **`DELETE /v1/projects/{ID}/milestones/{Milestone_ID}`**
+
+Permanently deletes a milestone. It cannot be undone.
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/477/milestones/2" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+
+### Returns
+
+| Code | Description
+| :--- | :----
+**200** `OK` | Indicates that the operation was successful and milestone is deleted successfully.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when the user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This indicates that the project or milestone does not exist.
+
+## Project Exception
+
+>Example Response
+
+```json
+{
+ "total_count":1,
+ "data":[
+ {
+ "id":2,
+ "name":"Working Sunday",
+ "description":"Working Sunday",
+ "date":"2018-11-17",
+ "is_working_exception":true,
+ "created_on":"2018-11-03T15:07:30.917087+05:30",
+ "modified_on":null,
+ "created_by":{
+ "id":2,
+ "name":"Patrick Wilson"
+ },
+ "modified_by":{
+ "id":null,
+ "name":null
+ },
+ "timings":[
+ {
+ "start_time":600,
+ "end_time":1080
+ }
+ ]
+ }
+ ]
+}
+```
+
+Exception is nothing but time duration that is different from a general schedule. eRS provides you the feature to add an exception to a project.
+
+Let's say there's a project with a calendar that doesn't have Sunday as a working day. But for some reason, work has to be done on the project on Sunday. In this case, it's a working exception. So, in such a situation, exceptions come in handy.
+
+
+eRS Cloud provides you two types of exceptions:
+
Working Exception :
Working Exception is added on a non-working day.
Non-working Exception :
Non-working Exception is added on a working day.
+
+_**Note**: Working Exception can be added without timings._
+
+ATTRIBUTES
+
+Name | Description
+ ---: | :----
+ **id** `integer` | eRS Cloud generated unique identifier for the exceptions object.|
+ **name** `string` | This field describes name of exception.|
+ **description** `string` | This field describes about the exception.|
+ **date** `string` | Date Field describes when will the exception get applied.|
+ **is_working_exception** `boolean`|Is working exception describes whether exception is a working exception or non working exception. True value means that exception is working exception and false value means that exception is non working exception.
+ **created_on** `string` | Time at which exception is created. |
+ **modified_on** `string` | Timestamp of the latest modification. |
+ **created_by** `object` | This field describes by whom exception is created .|
+ **modified_by** `object` | This field describes by whom the latest modification is done. |
+ **timings** `object` |Timings describe the timings of exception.
+
+
+
+### Retrieving exceptions
+
+> `GET v1/projects/{ID}/exceptions`
+
+> Example Request
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/12/exceptions" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "total_count":1,
+ "data":[
+ {
+ "id":2,
+ "name":"Working Sunday",
+ "description":"Working Sunday",
+ "date":"2018-11-17",
+ "is_working_exception":true,
+ "created_on":"2018-11-03T15:07:30.917087+05:30",
+ "modified_on":null,
+ "created_by":{
+ "id":2,
+ "name":"Patrick Wilson"
+ },
+ "modified_by":{
+ "id":null,
+ "name":null
+ },
+ "timings":[
+ {
+ "start_time":600,
+ "end_time":1080
+ }
+ ]
+ }
+ ]
+}
+```
+
+Retrieves the details of exceptions which are applied to the project. You only need to provide the unique project identifier that was returned upon project creation.
+
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This status code indicates that the operation was successful and exceptions retrieved successfully. |
+| **403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | Not Found error occurs when requested project does not exist (i.e. There is no project with given ID). This may also occur when requesting a project that has been deleted. |
+
+
+### Create an exception
+
+> `POST v1/projects/{ID}/exceptions`
+
+> Example Request
+
+```shell
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/12/exceptions" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "date": "2018-11-02",
+ "description": "Thursday 1",
+ "name": "Thursday 1",
+ "is_working_exception": true,
+ "timing_blocks":[
+ {
+ "start_time":600,
+ "end_time":1080
+ }
+ ]
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**date** `required`| Date Field describes when will the exception get applied. It is a `Date` type of field.
+**description** `optional`|As the name shows it is a description which we want to give for the exception . This field is a `string` type of field.
+**name** `required`|Name describes the name of exception. This field is a `string` type of field.
+**is_working_exception** `required`|Is working exception describes whether exception is a working exception or not. Accepts `true` if it is a working exception otherwise accepts `false` if it a non-working exception. This field is a `boolean` type of field.
+**timing_blocks** `optional`|Timing blocks describes the timings of exception. This field can be passed `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Array of objects` type of field.
+**timing_blocks.start_time** `optional`|Start time describes the start time of exception. This field can be passed `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Integer` type of field.
+**timing_blocks.end_time** `optional`|End time describes the end time of exception. This field can be passed `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Integer` type of field.
+
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+| **201** `Created` | This status code indicates that the operation was successful and exception created successfully.|
+| **400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters are or any unknown parameter is passed. |
+| **403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` |This status code indicates that project does not exist.|
+### Update an exception
+
+
+> `PUT v1/projects/{ID}/exceptions/{Exception_ID}`
+
+> Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/12/exceptions/2" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "date": "2018-11-02",
+ "description": "Thursday 1",
+ "name": "Thursday 1",
+ "is_working_exception": true,
+ "timing_blocks":[
+ {
+ "start_time":600,
+ "end_time":1080
+ }
+ ]
+ }'
+```
+
+
+
+Updates the specified project's exception by setting the value of the parameter passed. You need to provide the unique project identifier that was returned upon project creation and unique exception identifier that was returned upon exception addition. If parameter is not provided then it will be left unchanged.
+
+This request accepts mostly the same argument as the exception creation call.
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+ ---: | :----
+**date** `required`| Date Field describes when will the exception get applied. It is a `Date` type of field.
+**description** `optional`|As the name shows it is a description which we want to give for the exception . This field is a `string` type of field.
+**name** `required`|Name describes the name of exception. This field is a `string` type of field.
+**is_working_exception** `required`|Is working exception describes whether exception is working exception or not. Accepts `true` if it is working exception otherwise accepts `false` if it a non-working exception. This field is a `boolean` type of field
+**timing_blocks** `optional`|Timing blocks describes the timings of exception. This field can be pass `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Array of objects` type of field.
+**timing_blocks.start_time** `optional`|Start time describes the start time of exception. This field can be pass `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Integer` type of field.
+**timing_blocks.end_time** `optional`|End time describes the end time of exception. This field can be pass `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Integer` type of field.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This indicates that the operation was successful and a exception updated successfully.|
+| **400** `Bad Request` | Bad Request occurs when a request is not well-formed, syntactically incorrect, empty required parameters or any unknown parameter is passed.|
+| **403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` |This status code indicates that project or exception does not exist.|
+
+
+### Delete an exception
+
+> `DELETE v1/projects/{ID}/exceptions/{Exception_ID}`
+
+Permanently deletes an applied exception. It cannot be undone. You need to provide the unique project identifier that was returned upon project creation and unique exception identifier that was returned upon exception addition.
+
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/12/exceptions/2"\
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+
+
+| Code | Description
+| ---: | :----
+| **200** `OK` |This status code indicates that the operation was successful and exception deleted successfully. |
+| **404** `Not Found` |This status code indicates that project or exception does not exist.|
+
+## Project Notes
+
+To capture additional information about a project, eRS Cloud provides the `Notes`. If one has to provide any new information to a project which is not captured from the field, for such situations Notes are beneficial.
+
+ eRS Cloud API allows you to perform *`POST`*, *`GET`*, *`PUT`*, *`DELETE`* operations on Notes.
+
+_**Note**: The Notes Of Archived Project remain available for the records._
+
+ATTRIBUTES
+
+Name | Description
+ ---: | :----
+ **id** `integer` | eRS Cloud generated unique identifier for the notes. |
+ **content** `string` | Text written inside notes body.|
+ **created_on** `string` | Time at which the notes object is created. |
+ **modified_on** `string` | Describes the latest modification date.|
+ **created_by** `object` | This field describes by whom this note is created.|
+ **modified_by** `object` | This field describes by whom the modification is done.
+
+
+### List notes
+
+>` GET v1/projects/{ID}/notes`
+
+
+Retrieves the Notes list of specified project. You need to provide the unique project identifier that was returned upon project creation. The notes are returned which are sorted by lastly modified or added.
+
+> Example Request
+
+```shell
+curl -v -X GET "https://app.eresourcescheduler.cloud/rest/v1/projects/8/notes"\
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+>Example Request With Offset And Limit
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/8/notes?offset=1&limit=10"\
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+>Example Request With order_by
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/8/notes?offset=1&limit=10&order_by=created_on" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "total_count": 4,
+ "limit": 10,
+ "offset": 1,
+ "data": [
+ {
+ "id": 20,
+ "created_on": "2018-11-21T11:20:48.828322+05:30",
+ "content": "
Updated Content Value Given
",
+ "modified_on": null,
+ "created_by": {
+ "id": -99,
+ "name": "Testing User",
+ "image_uuid": null
+ },
+ "modified_by": {
+ "id": null,
+ "name": null
+ }
+ },
+ {...},
+ {...},
+ {...},
+ ]
+}
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+|**limit** `optional`| The limit keyword is used to limit the number of notes returned from a result set. *The default value of `limit` is* *`25`*. *Maximum value of limit can be* *`100.`* *If value of Limit is more than**`100`* *then it will set Maximum value of limit which is* *`100`*.
+|**offset** `optional`| The Offset value allows you to specify the ranking number of the first item on the page . The Offset value is most often used together with the Limit keyword. *The default value of `offset` is* *`0`* .|
+
+
+
+
+### Ordering the notes
+
+REQUEST QUERY PARAMETERS
+
+|Name|Options|Description|
+|-:|:-:|:-
+|**order_by** `optional`|
**created_on** *(Default)*
|List of notes will be returned and sorted by it's created date.|
+| |
modified_on
|List of notes will be returned and sorted by it's latest modified date.|
+
+
+### Returns
+
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This indicates that the operation was successful and returned list of notes. |
+| **400** `Bad Request` | Bad Request may occur when offset and limit value is negative.|
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | This status code indicates that project ID does not exist.|
+
+
+### Create a note
+
+>` POST v1/projects/{ID}/notes`
+
+
+> Example Request
+
+```shell
+
+curl -v -X POST "https://app.eresourcescheduler.cloud/rest/v1/projects/8/notes"\
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"\
+ -H "Content-Type: application/json"\
+ -d '{"content": "Hello Enbraun"}'
+```
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+ ---: | :----
+**content** `required` | To create new note you have to pass the body from content parameter. Content param accepts plain text. Also, you can pass text with HTML tags as Notes are Multi Line Rich Text.
+
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+| **201** `Created` | This status code indicates that the operation was successful and created a note successfully.|
+| **400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters are or any unknown parameter is passed. |
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+ **404** `Not Found` | This status code indicates that project does not exist.|
+
+
+
+
+### Update a note
+
+>` PUT v1/projects/{ID}/notes/{Note_ID}`
+
+Updates the specified project's note by setting the value of the parameter passed. You need to provide the unique project identifier that was returned upon project creation and unique note identifier that was returned upon note's creation. If parameter is not provided then it will be left unchanged.
+
+This request accepts mostly the same argument as the note creation call.
+
+> Example Request
+
+```shell
+
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest/v1/projects/8/notes/4"\
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"\
+ -H "Content-Type: application/json"\
+ -d '{"content": "Hello World"}'
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+ ---: | :----
+ **content** `required` | To update note you have to pass the body from `content` parameter. Content param accepts plain text. Also, you can pass text with HTML tags as Notes are Multi Line Rich Text.
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This indicates that the operation was successful and a note updated successfully.|
+| **400** `Bad Request` | Bad Request occurs when a request is not well-formed, syntactically incorrect, empty required parameters or any unknown parameter is passed.|
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | This status code indicates that project or note does not exist.|
+
+
+### Delete a note
+
+>` DELETE v1/projects/{ID}/notes/{Note_ID}`
+
+Permanently deletes a Note. It cannot be undone. You need to provide the unique project identifier that was returned upon project creation and unique note identifier that was returned upon note's creation.
+
+> Example Request
+
+```shell
+
+curl -v -X DELETE "https://app.eresourcescheduler.cloud/rest/v1/projects/8/notes/5"\
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+### Returns
+
+| Code | Description
+| ---: | :----
+| **200** `OK` |This status code indicates that the operation was successful and a note deleted successfully. |
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | This status code indicates that project or note does not exist.|
+
diff --git a/source/includes/_projecttypes.md b/source/includes/_projecttypes.md
new file mode 100644
index 00000000000..c2b44d69f17
--- /dev/null
+++ b/source/includes/_projecttypes.md
@@ -0,0 +1,323 @@
+# Project Types
+
+## Project type object
+
+> Example Response
+
+```json
+{
+ "id": 1,
+ "name": "Standard",
+ "description": "",
+ "color": "#000000;1",
+ "fields": [
+ {
+ "id": 39,
+ "code": "is_archive",
+ "display_name": "Archive",
+ "field_type": "ARCH",
+ "is_required": false,
+ "is_system_defined": true
+ },
+ {
+ "id": 40,
+ "code": "color",
+ "display_name": "Color",
+ "field_type": "COLPICK",
+ "is_required": false,
+ "is_system_defined": false
+ },
+ {
+ "id": 11,
+ "code": "email",
+ "display_name": "Email",
+ "field_type": "EMAIL",
+ "placeholder_text": "Enter valid email id",
+ "maxlength": 254,
+ "regex": "^[a-zA-Z]+[a-zA-Z0-9._]+@[a-zA-Z]+\.[a-zA-Z.]{2,5}$",
+ "is_required": false,
+ "is_system_defined": true
+ },
+ {
+ "id": 15,
+ "code": "end_date",
+ "display_name": "End Date",
+ "field_type": "DATE",
+ "is_required": false,
+ "is_system_defined": true,
+ "mindate": "1900-01-01",
+ "maxdate": "2099-12-31"
+ },
+ {
+ "id": 10,
+ "code": "title",
+ "display_name": "Project Name",
+ "field_type": "ENAME",
+ "minlength": 1,
+ "maxlength": 255,
+ "is_required": true,
+ "is_system_defined": true
+ },
+ {
+ "id": 101,
+ "code": "manager",
+ "display_name": "Manager",
+ "field_type": "DDSS",
+ "is_required": false,
+ "is_system_defined": false,
+ "options": [
+ {
+ "id": 107,
+ "name": "Chester Norman",
+ "description": null
+ },
+ {...}
+ ]
+ },
+ {
+ "id": 13,
+ "code": "project_start_date",
+ "display_name": "Start Date",
+ "field_type": "DATE",
+ "is_required": false,
+ "is_system_defined": true,
+ "mindate": "1900-01-01",
+ "maxdate": "2099-12-31"
+ },
+ {
+ "id": 32,
+ "code": "tags",
+ "display_name": "Tags",
+ "field_type": "TAGS",
+ "is_required": false,
+ "is_system_defined": true
+ }
+ ]
+}
+```
+Project type object represents the type of project. In an organization, there can be multiple types of projects. Administrator can add multiple project types using eRS Cloud application. Different project type objects can be configured to have a different sets of custom attributes as well, which allows customizing project objects to fit your requirements.
+
+ATTRIBUTES
+
+Name | Description
+| ---: | :---- |
+**id** `integer` |Unique identification number for the object, which allows referring to this object and can be used to search a particular project type.
+**name** `string` | Represents name for this object. This is used to identify object by using some meaningful phrase to describe type of projects like `Standard`, `Education` etc.
+**description** `string` | Description for project type object.
+**color** `string`| String representing hexadecimal color code assigned to the project type.
+**fields** `array of objects` |Represents collection of fields (or attributes) that are available for this project type. Each Project object of this project type can store / update values for these field. While creating or updating a Project user must pass arguments which are available for intended project type object.
+**fields.id** `integer` | Represents unique identification number of this field, which can be used to refer or search it.
+**fields.display_name** `string` |Name of this field to identify it.
+**fields.field_type** `string` | Represents the type of field. For example TEXT (for Text Field), INT (for Integer Number field), DDSS (for Dropdown Single Select Field), etc. See User Defined Fields to know more about different field types.
+**fields.code** `string` | It represents the unique code of the field which is referred as API code. This code acts as `key` in API response and the same must be used as `key` to pass values for a POST or PUT request.
+**fields.minlength** `integer` | Represents minimum no of characters in value this field can accept. Only applicable for text fields.
+**fields.maxlength** `integer` | Represents maximum no of characters in value this field can accept. Only applicable for text fields.
+**fields.regex** `string` | Represents regular expression which must be matched by value for this field. Only applicable for text fields.
+**fields.minnum** `integer` | Represents minimum value this field can accept. Only applicable for numeric fields.
+**fields.maxnum** `integer` | Represents maximum value this field can accept. Only applicable for numeric fields.
+**fields.mindate** `string` | Represents minimum value this field can accept. Only applicable for date / date time fields.
+**fields.maxdate** `string` | Represents maximum value this field can accept. Only applicable for date / date time field.
+**fields.is_required** `boolean` |Indicates whether this field is mandatory or not. If this field is a required field then a valid value for this field must be passed while creating such object and while updating object (if this field is intended to update).
+**is_system_defined** `boolean` | Indicates whether this field is system defined or a custom field. Fields which are system defined can not be customized.
+**fields.options** `string` |Field types such as Dropdown Single Select, Dropdown Multi Select, Radio Group etc. ( See User Defined Fields to know more. ) Allows user to pick one or more from these available options.
+**fields.options.id** `integer` | Represents unique identification number for the individual option object.
+**fields.options.name** `string` | Represents name or content of option object.
+**fields.options.color** `string` | Allows a user to store color code of option object. Only applicable for LABEL type fields.
+
+
+
+
+## Get a Specific Project Type
+
+Retrieves the details of an existing project-type. You only need to provide the unique project-type identifier that was returned upon project-type creation.
+
+
+> **`GET /v1/projecttypes/{ID}`**
+
+>Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/projecttypes/3" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+
+```
+
+> Example Response
+
+```json
+{
+
+ "id": 3,
+ "name": "Education",
+ "description": "",
+ "color": "#000000;1",
+ "fields": [
+ {
+ "id": 39,
+ "code": "is_archive",
+ "display_name": "Archive",
+ "field_type": "ARCH",
+ "is_required": false,
+ "is_system_defined": true
+ },
+ {
+ "id": 104,
+ "code": "department",
+ "display_name": "Department",
+ "field_type": "RDGRP",
+ "is_required": false,
+ "is_system_defined": false,
+ "options": [
+ {
+ "id": 117,
+ "name": "Accounts",
+ "description": null
+ },
+ {...}
+ ],
+ },
+ {
+ "id": 11,
+ "code": "email",
+ "display_name": "Email",
+ "field_type": "EMAIL",
+ "placeholder_text": "Enter valid email id",
+ "maxlength": 254,
+ "regex": "^[a-zA-Z]+[a-zA-Z0-9._]+@[a-zA-Z]+\.[a-zA-Z.]{2,5}$",
+ "is_required": false,
+ "is_system_defined": true
+ },
+ {
+ "id": 15,
+ "code": "end_date",
+ "display_name": "End Date",
+ "field_type": "DATE",
+ "is_required": false,
+ "is_system_defined": true,
+ "mindate": "1900-01-01",
+ "maxdate": "2099-12-31"
+ },
+ {
+ "id": 10,
+ "code": "title",
+ "display_name": "Project Name",
+ "field_type": "ENAME",
+ "minlength": 1,
+ "maxlength": 255,
+ "is_required": true,
+ "is_system_defined": true
+ },
+ {...},
+ {...}
+ ]
+}
+```
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This status code indicates that the operation was successful and a project-type get retrieved successfully . |
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` |This status code indicates that project-type ID does not exist.|
+
+
+## Get All Project Types
+
+Returns a list of project-types. The project-types are returned sorted by name.
+
+> **`GET /v1/projecttypes`**
+
+> Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/projecttypes" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+>Example Response
+
+```json
+{
+ "total_count": 4,
+ "data": [
+ {
+ "id": 3,
+ "name": "Education",
+ "description": "",
+ "color": "#000000;1",
+ "fields": [
+ {
+ "id": 39,
+ "code": "is_archive",
+ "display_name": "Archive",
+ "field_type": "ARCH",
+ "is_required": false,
+ "is_system_defined": true
+ },
+ {
+ "id": 104,
+ "code": "department",
+ "display_name": "Department",
+ "field_type": "RDGRP",
+ "is_required": false,
+ "is_system_defined": false,
+ "options": [
+ {
+ "id": 117,
+ "name": "Accounts",
+ "description": null
+ },
+ {...}
+ ],
+ },
+ {
+ "id": 11,
+ "code": "email",
+ "display_name": "Email",
+ "field_type": "EMAIL",
+ "placeholder_text": "Enter valid email id",
+ "maxlength": 254,
+ "regex": "^[a-zA-Z]+[a-zA-Z0-9._]+@[a-zA-Z]+\.[a-zA-Z.]{2,5}$",
+ "is_required": false,
+ "is_system_defined": true
+ },
+ {
+ "id": 15,
+ "code": "end_date",
+ "display_name": "End Date",
+ "field_type": "DATE",
+ "is_required": false,
+ "is_system_defined": true,
+ "mindate": "1900-01-01",
+ "maxdate": "2099-12-31"
+ },
+ {
+ "id": 10,
+ "code": "title",
+ "display_name": "Project Name",
+ "field_type": "ENAME",
+ "minlength": 1,
+ "maxlength": 255,
+ "is_required": true,
+ "is_system_defined": true
+ },
+ {...},
+ {...}
+ ]
+ },
+ {...},
+ {...}
+ ]
+}
+```
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This indicates that the operation was successful and list of project-types is returned. |
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
diff --git a/source/includes/_rates.md b/source/includes/_rates.md
new file mode 100644
index 00000000000..20c55cf1bc9
--- /dev/null
+++ b/source/includes/_rates.md
@@ -0,0 +1,842 @@
+# Rates
+
+This API is accessible only when financial module is active. If the keys connected to this API are used without having access to Financial Module then request will return client error status codes.
+
+## Resource Rates
+
+A rate is an entity that allows you to assign billing or cost rates to a resource object. Each resource has it's own set of billing and cost rate assigned on different effective dates.
+
+This API allows you to list, create, delete, update billing or cost rates of any resource.
+
+ATTRIBUTES
+
+
+Name | Description
+ ---: | :----
+**id** `integer` | Unique ID of resource object to which this rate belongs.
+**name** `string` | Name of resource object.
+**rates** `array of objects`| Represents collection of rates that are assigned on the resource object.
+**rates.id** `integer`| Auto generated unique identifier for rate object.
+**rates.rate** `float`| Represents applied rate.
+**rates.effective_date** `string`| Represents effective date for the rate.
+**rates.rate_type** `integer`| Represents rate type. Value of rate type is **1** for cost rate and **2** for billing rate. Both types of rate can be defined on the same `effective_date`.
+
+### Create Resource Rate
+
+Creates a new rate object for specified resource.
+
+>**`POST /v1/resources/{ID}/rates`**
+
+>Example Request
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/2/rates" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "cost_rate": 150,
+ "billing_rate": 300,
+ "effective_date": "2018-09-16"
+ }'
+
+```
+
+> Example Request For Replace Existing Rate
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/2/rates" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "cost_rate": 200,
+ "billing_rate": 350,
+ "effective_date": "2018-09-16",
+ "replace_existing_rate": true
+ }'
+
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+---: | :----
+**cost_rate** `*optional` | Represents cost rate. Rate value is a floating point number which could not be less than 0 and greater than 99999999.99.
+**billing_rate** `*optional` | Represents billing rate. Rate value is a floating point number which could not be less than 0 and greater than 99999999.99.
_**\*Note** : Either of the two rate types, i.e. `cost_rate` or `billing_rate` is necessary for creating rate._
+**effective_date** `required` | String representing date value for effective date of rate. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+**201** `Created` | Indicates that the operation was successful and rate created successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that resource does not exist.
+**409** `Conflict` | Conflict indicates that the rate can not be created because the same type of rate is already associated with passed effective date. If you wish to create rate of the same type any way you must use replace existing rate option by passing `true` for parameter `replace_existing_rate` or you can create rate of another type on given `effective_date`. This operation replaces existing rate with passed rate. Example request is shown to right.
+
+### List Resource Rates
+
+Retrieves list of all the rates on all resources.
+
+>**`GET /v1/resources/rates`**
+
+> Example Request
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/rates?\
+offset=1&limit=10" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Response
+
+ ```json
+{
+ "total_count": 18,
+ "limit": 10,
+ "offset": 1,
+ "data": [{
+ "id": 9,
+ "name": "Albert Murphy",
+ "rates":[
+ {
+ "id": 8,
+ "rate": 150,
+ "rate_type": 1,
+ "effective_date": "2019-01-01",
+ "created_on": "2018-08-20T09:20:34.925474Z",
+ "created_by":
+ {
+ "name": "John doe",
+ "id": 118
+ },
+ "modified_on": "2018-09-28T12:23:44.896426Z",
+ "modified_by":
+ {
+ "name": "John doe",
+ "id": 118
+ },
+ },
+ {
+ "id": 9,
+ "rate": 300,
+ "rate_type": 2,
+ "effective_date": "2019-01-01",
+ "created_on": "2018-08-20T09:30:34.925474Z",
+ "created_by":
+ {
+ "name": "John doe",
+ "id": 118
+ },
+ "modified_on": "2018-09-28T12:32:44.896426Z",
+ "modified_by":
+ {
+ "name": "John doe",
+ "id": 118
+ },
+ }
+ ]
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`25`** _Maximum value of `limit` can be_ **`500`**
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This status code indicates that the operation was successful and list of rates retrieved successfully.
+**400** `Bad Request` | Bad Request may occur when offset or limit value is negative.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested url is not correct or the data type of query parameters is not integer.
+
+
+
+
+
+
+
+### Search Resource Rates
+
+> **`POST /v1/resources/rates/search`**
+
+> Example Request For Filter In JSON Format
+
+```shell
+curl -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/rates/search" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "name:eq": "Albert Murphy"
+ }'
+```
+
+> Example Request For Filter By Passing Multiple Rules In JSON Format
+
+```shell
+curl -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/rates/search" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "name:eq": "Albert Murphy",
+ "roles:all": [3,6]
+ }'
+```
+
+Search Resource Rates API allows filtering the results returned in various ways. This enables a great power to find out what is needed. eRS Cloud API also allows filtering on custom defined fields with multiple operators and conditions to cover up complex scenarios for searching.
+
+A filter condition consists of three components which are **_field_**, **_operator_** and **_value_**. For example, fetching only those rates having `resource_type_id` 1, could be achieved by adding `"resource_type_id:eq": 1` to your query. If operator is not supplied, it takes default operator for field.
+
+Below is a list of available fields, which allow filtering rates:
+
+
+|**Field Code**| **Operator** | **Example**|
+|:--|:---|:--|
+**resource_type_id**|
| `"modified_on:eq": ["2021-07-08T00:00:00]` `"modified_on:lt": ["2021-07-08T00:00:00]` `"modified_on:gt": ["2021-07-08T59:59:59"]` `"modified_on:bt": ["2021-07-08T00:00:00", "2021-07-10T23:59:59"]` `"modified_on:bt": ["2021-07-08T00:00:00", ""]` `"modified_on:bt": ["", "2021-07-10T23:59:59"]` `"modified_on:ex": ["2021-07-08T00:00:00", "2021-07-10T23:59:59"]` `"modified_on:ex": ["2021-07-08T00:00:00", ""]` `"modified_on:ex": ["", "2021-07-10T23:59:59"]]`
+ _For filtering using custom fields and operators please check here._
+
+### Update Resource Rate
+
+>**`PUT /v1/resources/{ID}/rates/{RATE_ID}`**
+
+Updates an existing rate by setting the values of the parameters passed. Any parameters not passed will be left unchanged.
+
+This request accepts the same arguments as the rate creation call.
+
+>Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/8/rates/9" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "rate": 150,
+ "effective_date": "2018-09-16"
+ }'
+```
+
+> Example Request For Replace Existing Rate
+
+```shell
+
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/8/rates/9" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "rate": 250,
+ "effective_date": "2018-09-16",
+ "replace_existing_rate": true
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+---: | :----
+**rate** `optional` | Represents rate. Rate value is a floating point number which could not be less than 0 and greater than 99999999.99.
+**effective_date** `optional`| String representing date value for effective date of rate. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and rate updated successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that resource or rate does not exist.
+**409** `Conflict` | Conflict indicates that the rate can not be updated because the same type of rate is already associated with passed effective date. If you wish to update rate of the same type any way you must use replace existing rate option by passing `true` for parameter `replace_existing_rate` or you can update rate of another type on given effective date. This operation replaces existing rate with passed rate. Example request is shown to right.
+
+### Delete Resource Rate
+
+> **`DELETE /v1/resources/{ID}/rates/{RATE_ID}`**
+
+Permanently deletes a rate. It cannot be undone.
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/1/rates/2" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+### Return
+
+| Code | Description
+| :--- | :----
+**200** `OK` | Indicates that the operation was successful and rate deleted successfully.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This indicates that resource or rate does not exist.
+
+## Project Rates
+
+A rate is an entity that allows you to assign billing rates to a project object. Each project has it's own set of rates assigned on different effective dates.
+
+This API allows you to list, create, delete, update rates and billing status of any project.
+
+ATTRIBUTES
+
+
+Name | Description
+ ---: | :----
+**id** `integer` | Unique ID of project object to which this rate belongs.
+**title** `string` | Name of project object.
+**is_billable** `boolean`| Represents billing status of project object.
+**rates** `array of objects`| Represents collection of rates that are assigned on the project object. While creating or updating a rate object user must pass arguments which are available for this rate object.
+**rates.id** `integer`| Auto generated unique identifier for rate object.
+**rates.rate** `float`| Represents applied billing rate.
+**rates.effective_date** `string`| Represents effective date for the rate.
+
+### Create Project Rate
+
+Creates a new rate object for specified project.
+
+>**`POST /v1/projects/{ID}/rates`**
+
+>Example Request
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/2/rates" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "rate": 150,
+ "effective_date": "2018-09-16"
+ }'
+```
+> Example Request For Replace Existing Rate
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/2/rates" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "rate": 250,
+ "effective_date": "2018-09-16",
+ "replace_existing_rate": true
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+---: | :----
+**rate** `required` | Represents billing rate. Rate value is a floating point number which could not be less than 0 and greater than 99999999.99.
+**effective_date** `required` | String representing date value for effective date of rate. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+**201** `Created` | Indicates that the operation was successful and rate created successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that project does not exist.
+**409** `Conflict` | Conflict indicates that the rate can not be created because rate is already associated with passed effective date. If you wish to create rate of the same type any way you must use replace existing rate option by passing `true` for parameter `replace_existing_rate` which will replace existing rate with passed rate. Example request is shown to right.
+
+### List Project Rates
+
+Retrieves list of all the rates on all projects.
+
+>**`GET /v1/projects/rates`**
+
+> Example Request
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/rates?\
+offset=1&limit=10" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Response
+
+ ```json
+{
+ "total_count": 18,
+ "limit": 10,
+ "offset": 1,
+ "data": [{
+ "id": 9,
+ "title": "Project-A",
+ "is_billable": true,
+ "rates":[
+ {
+ "id": 8,
+ "rate": 150,
+ "effective_date": "2019-01-01",
+ "created_on": "2018-08-20T09:25:34.925474Z",
+ "created_by":
+ {
+ "name": "John doe",
+ "id": 118
+ },
+ "modified_on": "2018-09-28T12:32:44.896426Z",
+ "modified_by":
+ {
+ "name": "John doe",
+ "id": 118
+ },
+ }
+ ]
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`25`** _Maximum value of `limit` can be_ **`500`**
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This status code indicates that the operation was successful and list of rates retrieved successfully.
+**400** `Bad Request` | Bad Request may occur when offset or limit value is negative.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested url is not correct or the data type of query parameters is not integer.
+
+
+
+
+### Search Project Rates
+>**`POST /v1/projects/rates/search`**
+
+>Example Request For Filter In JSON Format
+
+```shell
+curl -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/rates/search" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "title:eq": "Project-A"
+ }'
+```
+
+> Example Request For Filter By Passing Multiple Rules In JSON Format
+
+```shell
+curl -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/rates/search" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "title:eq": "Project-A",
+ "project_start_date:gt": "2015-04-02"
+ }'
+```
+
+Search Project Rates API allows filtering the results returned in various ways. This enables a great power to find out what is needed. eRS Cloud API also allows filtering on custom defined fields with multiple operators and conditions to cover up complex scenarios for searching.
+
+A filter condition consists of three components which are **_field_**, **_operator_** and **_value_**. For example fetching only those rates having `project_type_id` 1, could be achieved by adding `"project_type_id":1 ` to your query. If operator is not supplied, it takes default operator for field. Read more
+
+Below is a list of available fields, which allow filtering rates:
+
+### Filters for System-defined fields
+
+|**Field Code**| **Operator** | **Example**|
+|:--|:---|:--|
+**project_type_id**|
| `"modified_on:eq": ["2021-07-08T00:00:00]` `"modified_on:lt": ["2021-07-08T00:00:00]` `"modified_on:gt": ["2021-07-08T59:59:59"]` `"modified_on:bt": ["2021-07-08T00:00:00", "2021-07-10T23:59:59"]` `"modified_on:bt": ["2021-07-08T00:00:00", ""]` `"modified_on:bt": ["", "2021-07-10T23:59:59"]` `"modified_on:ex": ["2021-07-08T00:00:00", "2021-07-10T23:59:59"]` `"modified_on:ex": ["2021-07-08T00:00:00", ""]` `"modified_on:ex": ["", "2021-07-10T23:59:59"]]`
+_For filtering using custom fields and operators please check here._
+
+### Update Project Rate
+
+>**`PUT /v1/projects/{ID}/rates/{RATE_ID}`**
+
+Updates an existing rate by setting the values of the parameters passed. Any parameters not passed will be left unchanged.
+
+This request accepts the same arguments as the rate creation call.
+
+>Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/8/rates/9" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "rate": 150,
+ "effective_date": "2018-09-16"
+ }'
+
+```
+> Example Request For Replace Existing Rate
+
+```shell
+
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/8/rates/9" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "rate": 250,
+ "effective_date": "2018-09-16",
+ "replace_existing_rate": true
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+---: | :----
+**rate** `optional` | Represents billing rate. Rate value is a floating point number which could not be less than 0 and greater than 99999999.99.
+**effective_date** `optional`| String representing date value for effective date of rate. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and rate updated successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that project or rate does not exist.
+**409** `Conflict` | Conflict indicates that the rate can not be updated as rate is already associated with passed effective date. If you wish to update rate of the same type any way you must use replace existing rate option by passing `true` for parameter `replace_existing_rate` which will replace existing rate with passed rate. Example request is shown to right.
+
+
+### Update Billing Status
+
+>**`PUT /v1/projects/{ID}/billingStatus`**
+
+Updates project billing status by setting the value of the `is_billable`.
+
+>Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/8/billingStatus" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "is_billable": true
+ }'
+
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**is_billable** `boolean`| Represents billing status of project. It's default value is true indicating the project is billable while false value indicates the project is non-billable.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and billing status updated successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that project does not exist.
+
+
+### Delete Project Rate
+
+> **`DELETE /v1/projects/{ID}/rates/{RATE_ID}`**
+
+Permanently deletes a rate. It cannot be undone.
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/projects/1/rates/2" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+### Return
+
+| Code | Description
+| :--- | :----
+**200** `OK` | Indicates that the operation was successful and rate deleted successfully.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This indicates that project or rate does not exist.
+
+
+## Role Rates
+
+A rate is an entity that allows you to assign billing or cost rates to a role object. Each role has it's own set of billing and cost rate assigned on different effective dates.
+
+This API allows you to list, create, delete, update rates of any role.
+
+ATTRIBUTES
+
+
+Name | Description
+ ---: | :----
+**id** `integer` | Unique ID of role object, which this rate belongs to.
+**name** `string` | Name of role object.
+**rates** `array of objects`| Represents collection of rates that are assigned on the project object. While creating or updating a rate object user must pass arguments which are available for this rate object.
+**rates.id** `integer`| Auto generated unique identifier for rate object.
+**rates.rate** `float`| Represents applied billing rate.
+**rates.effective_date** `string`| Represents effective date for the rate.
+**rates.rate_type** `integer`| Represents rate type. Value of rate type is **1** for cost rate and **2** for billing rate. Both types of rate can be defined on the same `effective_date`.
+
+### Create Role Rate
+
+Creates a new rate object for specified role.
+
+
+>**`POST /v1/roles/{ID}/rates`**
+
+>Example Request
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/roles/2/rates" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "cost_rate": 150,
+ "billing_rate": 300,
+ "effective_date": "2018-09-16"
+ }'
+```
+
+> Example Request For Replace Existing Rate
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/roles/2/rates" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "cost_rate": 200,
+ "billing_rate": 350,
+ "effective_date": "2018-09-16",
+ "replace_existing_rate": true
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+---: | :----
+**cost_rate** `*optional` | Represents cost rate. Rate value is a floating point number which could not be less than 0 and greater than 99999999.99.
+**billing_rate/rate** `*optional` | Represents billing rate. Rate value is a floating point number which could not be less than 0 and greater than 99999999.99.
_**\*Note** : Either of the two rate types, i.e. `cost_rate` or `billing_rate` is necessary for creating rate._
+**effective_date** `required` | String representing date value for effective date of rate. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+**201** `Created` | Indicates that the operation was successful and rate created successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that role does not exist.
+**409** `Conflict` | Conflict indicates that the rate can not be created because the same type of rate is already associated with passed effective date. If you wish to create rate of the same type any way you must use replace existing rate option by passing `true` for parameter `replace_existing_rate` or you can create rate of another type on given `effective_date`. This operation replaces existing rate with passed rate. Example request is shown to right.
+
+
+### List Role Rates
+
+Retrieves list of all the rates on all roles.
+
+>**`GET /v1/roles/rates`**
+
+> Example Request
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/roles/rates?\
+offset=1&limit=10" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Response
+
+ ```json
+{
+ "total_count": 18,
+ "limit": 10,
+ "offset": 1,
+ "data": [{
+ "id": 9,
+ "name": "Architect",
+ "rates":[
+ {
+ "id": 8,
+ "rate": 150,
+ "rate_type": 1,
+ "effective_date": "2019-01-01",
+ "created_on": "2018-08-20T09:25:34.925474Z",
+ "created_by":
+ {
+ "name": "John doe",
+ "id": 118
+ },
+ "modified_on": "2018-09-28T12:32:44.896426Z",
+ "modified_by":
+ {
+ "name": "John doe",
+ "id": 118
+ },
+ },
+ {
+ "id": 9,
+ "rate": 250,
+ "rate_type": 2,
+ "effective_date": "2019-01-01",
+ "created_on": "2018-08-20T09:25:34.925474Z",
+ "created_by":
+ {
+ "name": "John doe",
+ "id": 118
+ },
+ "modified_on": "2018-09-28T12:32:44.896426Z",
+ "modified_by":
+ {
+ "name": "John doe",
+ "id": 118
+ },
+ }
+ ]
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`25`** _Maximum value of `limit` can be_ **`500`**
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This status code indicates that the operation was successful and list of rates retrieved successfully.
+**400** `Bad Request` | Bad Request may occur when offset or limit value is negative.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested url is not correct or the data type of query parameters is not integer.
+
+
+
+### Update Role Rate
+
+>**`PUT /v1/roles/{ID}/rates/{RATE_ID}`**
+
+Updates an existing rate by setting the values of the parameters passed. Any parameters not passed will be left unchanged.
+
+This request accepts the same arguments as the rate creation call.
+
+>Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/roles/8/rates/9" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "rate": 150,
+ "effective_date": "2018-09-16"
+ }'
+
+```
+
+> Example Request For Replace Existing Rate
+
+```shell
+
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/roles/8/rates/9" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "rate": 250,
+ "effective_date": "2018-09-16",
+ "replace_existing_rate": true
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+---: | :----
+**rate** `required` | Represents billing rate. Rate value is a floating point number which could not be less than 0 and greater than 99999999.99.
+**effective_date** `optional`| String representing date value for effective date of rate. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and rate updated successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This status code indicates that role or rate does not exist.
+**409** `Conflict` | Conflict indicates that the rate can not be updated because the same type of rate is already associated with passed effective date. If you wish to update rate of the same type any way you must use replace existing rate option by passing `true` for parameter `replace_existing_rate` or you can update rate of another type on given `effective_date`. This operation replaces existing rate with passed rate. Example request is shown to right.
+
+
+### Delete Role Rate
+
+> **`DELETE /v1/roles/{ID}/rates/{RATE_ID}`**
+
+Permanently deletes a rate. It cannot be undone.
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/roles/1/rates/2" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+### Return
+
+| Code | Description
+| :--- | :----
+**200** `OK` | Indicates that the operation was successful and rate deleted successfully.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | This indicates that role or rate does not exist.
\ No newline at end of file
diff --git a/source/includes/_requirement.md b/source/includes/_requirement.md
new file mode 100644
index 00000000000..8ed9fe97932
--- /dev/null
+++ b/source/includes/_requirement.md
@@ -0,0 +1,875 @@
+# Requirement
+
+## Requirement Object
+
+>Example Response
+
+```json
+{
+ "id": 251,
+ "project": {
+ "id": 2,
+ "title": "Mars Rover"
+ },
+ "task": {
+ "name": "Data Processing",
+ "id": 7
+ },
+ "role": {
+ "name": "Tax Manager",
+ "id": 11
+ },
+ "start_time": "2023-08-21T09:00:00",
+ "end_time": "2023-08-22T17:00:00",
+ "effort": 32,
+ "unit": 2,
+ "tags": [
+ "London",
+ "onsite"
+ ],
+ "assignments": [ {
+ "booking_id": 3306,
+ "resource": {
+ "id": 126,
+ "name": "Oliver"
+ },
+ "start_time": "2023-09-20T09:00:00",
+ "end_time": "2023-09-25T17:15:00",
+ "effort_hrs": 16.12
+ }, {
+ "booking_id": 3305,
+ "resource": {
+ "id": 140,
+ "name": "Thomas"
+ },
+ "start_time": "2023-09-20T09:00:00",
+ "end_time": "2023-09-25T17:15:00",
+ "effort_hrs": 16.3
+ } ],
+ "flexi_range_duration": 5,
+ "flexi_range_unit": 2,
+ "allow_multi_allocation": true,
+ "sync_to_booking": true,
+ "conditions": [ {
+ "operator": "all",
+ "field": "udf_skills",
+ "values": [ {
+ "name": "Account Reconciliation",
+ "description": null,
+ "id": 34
+ }, {
+ "name": "Account Taxation",
+ "description": null,
+ "id": 23
+ } ],
+ "weightage": 10,
+ "is_mandatory": true
+ }, {
+ "operator": "any",
+ "field": "udf_city",
+ "values": [ {
+ "name": "London",
+ "description": null,
+ "id": 361
+ }, {
+ "name": "Dublin",
+ "description": null,
+ "id": 362
+ } ],
+ "weightage": 10,
+ "is_mandatory": false
+ } ],
+ "created_on": "2023-09-15T09:03:33.505344Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2023-09-15T09:05:12.314058Z",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ }
+}
+```
+
+`Requirement` object represents a role request for a specific project or task within a defined time range.
+
+ATTRIBUTES
+
+Following attributes are available for requirement object. To know about attributes currently applied for requirement object please check Requirement Profile API.
+
+Name | Description
+ ---: | :----
+**id** `integer` | eRS Cloud generated unique identifier for the requirement object.
+**project** `object` | Project object for which this requirement was created.
+**task** `object` | Task object defines what needs to be done.These tasks can be selected from the predefined tasks within the project associated with the requirement.
+**role** `object` | Role object defines which role resource needs to perform for this requirement.
+**start_time** `string` | Represents the starting date and time of the requirement.
+**end_time** `string` | Represents the ending date and time of the requirement.
+**effort** `float` | Represents the effort value for the requirement.
+**unit** `integer` | Represents unit of effort for the requirement. Unit could be one of `Hours` or `Full Time Equivalent`.
+**tags** `array of strings` | Tags are strings (labels) associated with this requirement object which could be used for the purpose of identification or other information.
+**assignments** `array of object` | This refers to resources that have been allocated to fulfill the requirements of the project or task.
**assignments.booking_id** `integer` ID of the booking object on which the resource has been assigned against the requirement.
**assignments.resource** `object` ID and name of the resource that has been assigned to the requirement.
**assignments.start_time** `string` Represents the start date and time of the booking object of the assigned resource.
**assignments.end_time** `string` Represents the end date and time of the booking object of the assigned resource.
**assignments.effort_hrs** `float` Represents the effort value required from the assigned resource for the project in the booking object.
+**flexi_range_duration** `integer` | Represents the defined duration range for flexibility in fulfilling the requirement compared to the original requirement date.
+**flexi_range_unit** `integer` | Represents a unit that allows for flexibility in fulfilling the requirement. Unit value could be one of the following:
**1** for `Hours` : Refers to 'hours' as a unit.
**2** for `Days` : Refers to 'days' as a unit.
+**allow_multi_allocation** `boolean` | This refers to allocation of a specific requirement to multiple assignment.
+**sync_to_booking** `boolean` | This setting indicates whether the values of common custom fields in the bookings corresponding to this requirement are always in sync. When turned on, users will not be able to modify the common custom fields in the booking form, and the values will always be taken from the linked requirement.
+**conditions** `array of object` | This refers to the criteria on which the requirement must be fulfilled.
**conditions.field** `string` This is a reference to the text's API_code.
**conditions.operator** `string` This refers to a character that represents a specific mathematical or logical action or process.
**conditions.values** This refers to the values defined for the requirement to be considered in suggested resources.
**conditions.weightage** `integer` Every condition can be assigned relative importance in comparison to other conditions to calculate its weightage. Weightage is ultimately used to calculate the match score of resources.
**conditions.is_mandatory** `boolean` Indicates whether this field is mandatory. If this field is marked as mandatory, it means that a required value must be provided for it in the suggested resources.
+**created_on** `string` | Timestamp at which this requirement object was created.
+**created_by** `object` | Object representing user who created this requirement object.
+**modified_on** `string` | Represents latest modification timestamp.
+**modified_by** `object` | Object representing most recent user who modified this requirement object.
+**udf_\*** | Custom user-defined fields are used to capture additional information of requirement. User-defined fields can be of multiple types. Custom fields are highly useful for optimally configuring requirement objects. In the given example response, all keys starting with the prefix `udf_` are user-defined custom fields. Learn more
+
+## Create a Requirement
+
+> **`POST v1/requirements`**
+
+
+> Example Request:
+
+```shell
+ curl -v -X POST "https://app.eresourcescheduler.cloud/rest/v1/requirements" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "project_id": 1,
+ "task_id": 1,
+ "role_id": 7,
+ "start_time": "2023-10-02T00:00:00",
+ "end_time": "2023-10-03T00:00:00",
+ "udf_confirmed": true,
+ "effort": 3,
+ "unit": 4,
+ "tags": ["London","Onsite"] ,
+ "flexi_range_duration": 5,
+ "flexi_range_unit": 2,
+ "allow_multi_allocation": true,
+ "sync_to_booking": true,
+ "conditions": [{
+ "field": "udf_qualification",
+ "operator": "any",
+ "values": [334,337],
+ "weightage": 40,
+ "is_mandatory": true
+ }, {
+ "field": "udf_experiences",
+ "operator": "eq",
+ "values": 5,
+ "weightage": 40,
+ "is_mandatory": true
+ }
+ ]
+ }'
+```
+
+Creates a new requirement object.
+
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**project_id** `required` | ID of the project object for which this requirement object is being created.
+**task_id** ⚑⚑| ID of the task object within the project that needs to be done in this requirement.
+**role_id** ⚑⚑| ID of the role object that the resource needs to perform for the requirement. Role can be either the performing role or non-performing role of the resource.
+**start_time** `required` | Represents start date and time for requirement object. This field accepts value in ISO 8601 format for date-time i.e. yyyy-MM-ddThh:mm:ss. The value must be snapped in 15 minutes interval, which effectively means that minutes values should be one of(00/15/30/45) and seconds value should always be 0. (if given).
+**end_time** `required` | Represents end date and time for requirement object. This field accepts value in ISO 8601 format for date-time i.e. yyyy-MM-ddThh:mm:ss. The value must be snapped in 15 minutes interval, which effectively means that minutes values should be one of(00/15/30/45) and seconds value should always be 0. (if given). `end_time` must always be ahead of `start_time` by at least 15 minutes as a requirement of less than 15 minutes is not allowed.
+**effort** `required`|Represents the effort value for the requirement.This defines how much effort is needed to complete the task. Effort value is a floating-point number that cannot be less than 0 or greater than 99999999.99. If effort value is not provided system will take default value 0.
+**unit** `required` | Integer number (2 or 4) represents the unit in which effort is defined. The unit value can be one of the following:
**2** for `Hours` : This defines `effort` value in fixed hours which doesn't change upon changes in requirement.
**4** for `Full Time Equivalent` : Full time equivalent is calculated using FTE calendar defined in Administrator calendar settings. Capacity from FTE calendar for defined time in requirement, is considered as 1 FTE.
+**tags** ⚑ |Tags are strings (labels) associated with this requirement object which could be used for the purpose of identification or other information.
+**flexi_range_duration** `integer` |Represents the defined duration range for flexibility in fulfilling the requirement compared to the original requirement date.
+**flexi_range_unit** `integer` | Represents a unit that allows for flexibility in fulfilling the requirement. Unit value could be one of the following:
**1** for `Hours` : Refers to 'hours' as a unit
**2** for `Days` : Refers to 'days' as a unit
+**allow_multi_allocation** `boolean` | This refers to allocation of a specific requirement to multiple resources simultaneously.
+**sync_to_booking** `boolean` | This setting indicates whether the values of common custom fields in the bookings corresponding to this requirement are always in sync. When turned on, users will not be able to modify the common custom fields in the booking form, and the values will always be taken from the linked requirement.
+**conditions** `array of object` | This refers to the criteria on which the requirement must be fulfilled.
**conditions.field** `string` This is a reference to the text's API_code.
conditions.operator`string` This refers to a character that represents a specific mathematical or logical action or process.
**conditions.values** This refers to the values defined for the requirement to be considered in suggested resources.
**conditions.weightage** `integer` Every condition can be assigned relative importance in comparison to other conditions to calculate its weightage. Weightage is ultimately used to calculate the match score of resources.
**conditions.is_mandatory** `boolean` Indicates whether this field is mandatory. If this field is marked as mandatory, it means that a required value must be provided for it in the suggested resources.
+**udf_\*** ⚑⚑ | A user with Administrator rights can add custom fields. These fields can be used to capture additional information in Requirements. The value for a user defined field can be passed as shown in example request. In given example `udf_confirmed` is a user defined field. Learn more
_**Note**: User with Administrator rights can make fields marked with ⚑ mandatory and remove fields marked with ⚑, from requirement profile using eRS Cloud Application. If mandatory fields are not passed with a valid value or if removed fields are passed while creating requirement, the operation will fail with response code **400**_.
+
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+| **201** `Created` | This status code indicates that the operation was successful and a requirement is created successfully.|
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed. Additionally, Bad request may also occur in one of these conditions:
Project is marked as Archived.
Duration of requirement is more than allowed requirement duration set by Administrator using ers Cloud Application in Administrator Requirement Settings.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+
+## List Requirements
+
+Returns list of requirements. The requirements are returned sorted by requirement's `start_time` and ID.
+
+> **`GET /v1/requirements`**
+
+> Example Request
+
+```shell
+curl -v GET "https://app.eresourcescheduler.cloud/rest/v1/requirements?\
+start=2023-01-01&end=2023-12-31" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+>Example Request With Offset And Limit
+
+```shell
+curl -v GET "https://app.eresourcescheduler.cloud/rest/v1/requirements?\
+start=2023-01-01&end=2023-12-31&offset=1&limit=10" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "total_count": 7,
+ "data": [{
+ "id": 251,
+ "project": {
+ "id": 2,
+ "title": "Mars Rover"
+ },
+ "task": {
+ "name": "Data Processing",
+ "id": 7
+ },
+ "role": {
+ "name": "Tax Manager",
+ "id": 11
+ },
+ "start_time": "2023-08-21T09:00:00",
+ "end_time": "2023-08-22T17:00:00",
+ "effort": 32,
+ "unit": 2,
+ "tags": [
+ "London",
+ "onsite"
+ ],
+ "assignments": [ {
+ "booking_id": 3306,
+ "resource": {
+ "id": 126,
+ "name": "Oliver"
+ },
+ "start_time": "2023-09-20T09:00:00",
+ "end_time": "2023-09-25T17:15:00",
+ "effort_hrs": 16.12
+ }, {
+ "booking_id": 3305,
+ "resource": {
+ "id": 140,
+ "name": "Thomas"
+ },
+ "start_time": "2023-09-20T09:00:00",
+ "end_time": "2023-09-25T17:15:00",
+ "effort_hrs": 16.3
+ } ],
+ "flexi_range_duration": 5,
+ "flexi_range_unit": 2,
+ "allow_multi_allocation": true,
+ "sync_to_booking": true,
+ "conditions": [ {
+ "operator": "all",
+ "field": "udf_skills",
+ "values": [ {
+ "name": "Account Reconciliation",
+ "description": null,
+ "id": 34
+ }, {
+ "name": "Account Taxation",
+ "description": null,
+ "id": 23
+ } ],
+ "weightage": 10,
+ "is_mandatory": true
+ }, {
+ "operator": "any",
+ "field": "udf_city",
+ "values": [ {
+ "name": "London",
+ "description": null,
+ "id": 361
+ }, {
+ "name": "Dublin",
+ "description": null,
+ "id": 362
+ } ],
+ "weightage": 10,
+ "is_mandatory": false
+ } ],
+ "created_on": "2023-09-15T09:03:48.428713+00:00",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2023-09-15T09:05:40.515333+00:00",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ }
+ },
+ { ... },
+ { ... }
+ ]
+ }
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`100`**. _Maximum value of `limit` can be_ **`500`**.
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**.
+**start** `optional` | String value representing start date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter requirements starting on or after this date.
+**end** `optional` | String value representing end date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter requirements starting before this date.
+||_**Note**: By default if `start` & `end` arguments are omitted, then requirements of current month will be returned. If requirements of a certain period are needed, then both `start` & `end` arguments required. If only one argument `start` or `end` is passed then a bad request error is raised._
+
+
+### Returns
+
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` |This indicates that the operation was successful and list of requirements is returned. |
+**400** `Bad Request` | Bad Request may occur when offset or limit value is negative integer.|
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+
+
+## Retrieve a Requirement
+
+> **`GET v1/requirements/{ID}`**
+
+> Example Request
+
+```shell
+curl -v -X GET "https://app.eresourcescheduler.cloud/rest/v1/requirements/251" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "id": 251,
+ "project": {
+ "id": 2,
+ "title": "Mars Rover"
+ },
+ "task": {
+ "name": "Data Processing",
+ "id": 7
+ },
+ "role": {
+ "name": "Tax Manager",
+ "id": 11
+ },
+ "start_time": "2023-08-21T09:00:00",
+ "end_time": "2023-08-22T17:00:00",
+ "effort": 32,
+ "unit": 2,
+ "tags": [
+ "London",
+ "onsite"
+ ],
+ "assignments": [ {
+ "booking_id": 3306,
+ "resource": {
+ "id": 126,
+ "name": "Oliver"
+ },
+ "start_time": "2023-09-20T09:00:00",
+ "end_time": "2023-09-25T17:15:00",
+ "effort_hrs": 16.12
+ }, {
+ "booking_id": 3305,
+ "resource": {
+ "id": 140,
+ "name": "Thomas"
+ },
+ "start_time": "2023-09-20T09:00:00",
+ "end_time": "2023-09-25T17:15:00",
+ "effort_hrs": 16.3
+ } ],
+ "flexi_range_duration": 5,
+ "flexi_range_unit": 2,
+ "allow_multi_allocation": true,
+ "sync_to_booking": true,
+ "conditions": [ {
+ "operator": "all",
+ "field": "udf_skills",
+ "values": [ {
+ "name": "Account Reconciliation",
+ "description": null,
+ "id": 34
+ }, {
+ "name": "Account Taxation",
+ "description": null,
+ "id": 23
+ } ],
+ "weightage": 10,
+ "is_mandatory": true
+ }, {
+ "operator": "any",
+ "field": "udf_city",
+ "values": [ {
+ "name": "London",
+ "description": null,
+ "id": 361
+ }, {
+ "name": "Dublin",
+ "description": null,
+ "id": 362
+ } ],
+ "weightage": 10,
+ "is_mandatory": false
+ } ],
+ "created_on": "2023-09-15T09:03:48.428713+00:00",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2023-09-15T09:05:40.515333+00:00",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ }
+}
+```
+Retrieves the details of an existing requirement. You only need to provide the unique requirement identifier that was returned upon requirement creation.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This status code indicates that the operation was successful and a requirement returned successfully.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested requirement does not exist (i.e. There is no requirement with given ID). This may also occur when requesting a requirement that has been deleted.
+
+## Search Requirements
+
+
+
+> **`POST /v1/requirements/search`**
+
+> Example Request For Filter In JSON Format
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/requirements/search?\
+start=2023-01-01&end=2023-12-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "requirement":{
+ "role_id:any":1
+ }
+ }'
+```
+
+> Example Request For Filter By Passing Multiple Filters In JSON Format
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/requirements/search?\
+start=2023-01-01&end=2023-12-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "project":{"id:eq":1},
+ "requirement":{"role_id:any":1},
+ "task":{"id:any":[2,3]}
+ }'
+```
+
+> Example Response
+
+```json
+{
+ "total_count": 3,
+ "data": [{
+ "id": 249,
+ "project": {
+ "id": 1,
+ "title": "Apollo 11"
+ },
+ "task": {
+ "name": "Data Handling",
+ "id": 3
+ },
+ "role": {
+ "name": "Project Manager",
+ "id": 1
+ },
+ "start_time": "2023-09-21T09:00:00",
+ "end_time": "2023-09-22T17:00:00",
+ "effort": 32,
+ "unit": 2,
+ "tags": [
+ "London",
+ "onsite"
+ ],
+ "assignments": null,
+ "flexi_range_duration": 5,
+ "flexi_range_unit": 2,
+ "allow_multi_allocation": true,
+ "sync_to_booking": false,
+ "conditions": [ {
+ "operator": "all",
+ "field": "udf_skills",
+ "values": [ {
+ "name": "Account Reconciliation",
+ "description": null,
+ "id": 34
+ }, {
+ "name": "Account Taxation",
+ "description": null,
+ "id": 23
+ } ],
+ "weightage": 10,
+ "is_mandatory": true
+ }, {
+ "operator": "any",
+ "field": "udf_city",
+ "values": [ {
+ "name": "London",
+ "description": null,
+ "id": 361
+ }, {
+ "name": "Dublin",
+ "description": null,
+ "id": 362
+ } ],
+ "weightage": 10,
+ "is_mandatory": false
+ } ],
+ "created_on": "2023-09-15T09:03:48.428713+00:00",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2023-09-15T09:05:40.515333+00:00",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ }
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`100`**. _Maximum value of `limit` can be_ **`500`**.
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**.
+**start** `optional` | String value representing start date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter requirements starting on or after this date.
+**end** `optional` | String value representing end date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter requirements starting before this date.
+||_**Note**: By default if `start` & `end` arguments are omitted, then requirements of current month will be returned. If requirements of a certain period are needed, then both `start` & `end` arguments required. If only one argument `start` or `end` is passed then a bad request error is raised._
+
+Search Requirement API allows filtering the results set in various ways. This enables a great power to find out what is needed. eRS Cloud API also allows filtering on custom defined fields with multiple operators and conditions to cover up complex scenarios for searching.
+
+A filter condition consists of three components which are **_field_**, **_operator_** and **_value_**. For example, fetching only those requirements having tag `tagA` or `tagB`, could be achieved by adding `"tags:any": ["tagA", "tagB"]` to request body. If operator is not supplied, it takes default operator for field.
+
+Below is a list of available fields, which allow filtering requirements:
+
+|**Field Type** | **Operator** | **Example**|
+:--| :--- | :--- | :--- |
+**tags**|
| `"modified_on:eq": ["2021-07-08T00:00:00"]` `"modified_on:lt": ["2021-07-08T00:00:00"]` `"modified_on:gt": ["2021-07-08T59:59:59"]` `"modified_on:bt": ["2021-07-08T00:00:00", "2021-07-10T23:59:59"]` `"modified_on:bt": ["2021-07-08T00:00:00", ""]` `"modified_on:bt": ["", "2021-07-10T23:59:59"]` `"modified_on:ex": ["2021-07-08T00:00:00", "2021-07-10T23:59:59"]` `"modified_on:ex": ["2021-07-08T00:00:00", ""]` `"modified_on:ex": ["", "2021-07-10T23:59:59"]]`
+_Additionally, requirements can also be filtered using project fields and custom fields of requirements. An example request for fetching only requirement having `project_id` as 1 and `role_id` as 1 is shown._
+## Update a Requirement
+
+Updates the specified requirement by setting values of parameters passed. Values of any parameters which are not provided will be unchanged. To unset existing value for a parameter, just pass an empty value i.e. `null`.
+
+> **`PUT /v1/requirements/{ID}`**
+
+> Example Request
+
+```shell
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest/v1/requirements/251" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "project_id": 1,
+ "start_time": "2023-08-15T09:00:00",
+ "end_time":"2023-08-15T17:00:00",
+ "effort": 8,
+ "role_id":3,
+ "unit": 2,
+ "conditions": [
+ {
+ "field":"udf_qualification",
+ "operator":"any",
+ "values":[18,26],
+ "weightage":20,
+ "is_mandatory":false}
+ ]
+}'
+```
+
+> Example Request: Update a requirement and unlinking its linked bookings
+
+```shell
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest/v1\
+/requirements/106?unlink_bookings=true" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "task_id":4,
+ "role_id":1,
+ "start_time":"2023-10-10T09:00:00",
+ "end_time":"2023-10-13T17:00:00"
+ }'
+```
+
+> Example Request: Update a requirement and deleting its linked bookings
+
+```shell
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest/v1\
+/requirements/106?delete_bookings=true" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "task_id":4,
+ "role_id":1,
+ "start_time":"2023-10-10T09:00:00",
+ "end_time":"2023-10-13T17:00:00"
+ }'
+```
+
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**project_id** `required` | ID of the project object for which this requirement object is being created. This will throw an error if you post an empty value.
+**task_id** ⚑⚑| ID of the task object within the project that needs to be done in this requirement.
+**role_id** ⚑⚑| ID of the role object that the resource needs to perform for the requirement. Role can be either the performing role or non-performing role of the resource.
+**start_time** `required` | Represents start date and time for requirement object. This field accepts value in ISO 8601 format for date-time i.e. yyyy-MM-ddThh:mm:ss. The value must be snapped in 15 minutes interval, which effectively means that minutes values should be one of(00/15/30/45) and seconds value should always be 0. (if given). This will throw an error if you post an empty value.
+**end_time** `required` | Represents end date and time for requirement object. This field accepts value in ISO 8601 format for date-time i.e. yyyy-MM-ddThh:mm:ss. The value must be snapped in 15 minutes interval, which effectively means that minutes values should be one of(00/15/30/45) and seconds value should always be 0. (if given). `end_time` must always be ahead of `start_time` by at least 15 minutes as a requirement of less than 15 minutes is not allowed. This will throw an error if you post an empty value.
+**effort** `required` |Represents the effort value for the requirement.This defines how much effort is needed to complete the task. Effort value is a floating-point number that cannot be less than 0 or greater than 99999999.99. If effort value is not provided system will take default value 0.
+**unit** `required` | Integer number (2 or 4) represents the unit in which effort is defined. The unit value can be one of the following:
**2** for `Hours` : This defines `effort` value in fixed hours which doesn't change upon changes in requirement.
**4** for `Full Time Equivalent` : Full time equivalent is calculated using FTE calendar defined in Administrator calendar settings. Capacity from FTE calendar for defined time in requirement, is considered as 1 FTE.
+**tags** `array of strings` |Tags are strings (labels) associated with this requirement object which could be used for the purpose of identification or other information.
+**flexi_range_duration** `integer` | Represents the defined duration range for flexibility in fulfilling the requirement compared to the original requirement date.
+**flexi_range_unit** `integer` | Represents a unit that allows for flexibility in fulfilling the requirement. Unit value could be one of the following:
**1** for `Hours` : Refers to 'hours' as a unit.
**2** for `Days` : Refers to 'days' as a unit.
+**allow_multi_allocation** `boolean` | This refers to allocation of a specific requirement to multiple resources simultaneously.
+**sync_to_booking** `boolean` | This setting indicates whether the values of common custom fields in the bookings corresponding to this requirement are always in sync. When turned on, users will not be able to modify the common custom fields in the booking form, and the values will always be taken from the linked requirement.
+**conditions** `array of object` | This refers to the criteria on which the requirement must be fulfilled.
**conditions.field** `string` This is a reference to the text's API_code.
conditions.operator`string` This refers to a character that represents a specific mathematical or logical action or process.
**conditions.values** This refers to the values defined for the requirement to be considered in suggested resources.
**conditions.weightage** `integer` Every condition can be assigned relative importance in comparison to other conditions to calculate its weightage. Weightage is ultimately used to calculate the match score of resources.
**conditions.is_mandatory** `boolean` Indicates whether this field is mandatory. If this field is marked as mandatory, it means that a required value must be provided for it in the suggested resources.
+**udf_\*** ⚑⚑ | A user with Administrator rights can add custom fields. These fields can be used to capture additional information in requirements. Learn more.
_**Note**: User with Administrator rights can make fields marked with ⚑ mandatory and remove fields marked with ⚑, from requirement profile using eRS Cloud Application. If mandatory fields are not passed with a valid value or if removed fields are passed while updating requirement, the operation will fail with response code **400**_.
+
+
+### Returns
+
+
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This indicates that the operation was successful and a requirement updated successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, empty required parameters or any unknown parameter is passed. Additionally, Bad request may also occur in one of these conditions:
Trying to update `start_time` or `end_time` such that `end_time` gets earlier than `start_time`.
Trying to update requirements of archived project.
Duration of requirement is more than allowed requirement duration set by Administrator using ers Cloud Application in Administrator Requirement Settings.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested requirement does not exist (i.e. There is no requirement with given ID). This may also occur when requesting a requirement that has been deleted.
+**409** `Conflict` | Conflict indicates that when you are updating a requirement linked to booking(s), then you must pass one of the parameters i.e; `delete_bookings=true` to delete requirement and respective booking or another parameter `unlink_bookings=true` will update requirement after unlinking the respective bookings. this action will be performed through Administrator Requirement Settings.
+
+
+
+
+## Requirement Operator
+
+
+> Example for Conditions (resource_type_id)
+
+```shell
+{
+ ...
+ ...
+ "conditions": [{
+ "field":"resource_type_id",
+ "operator":"any",
+ "values":[2,3],
+ "weightage":10,
+ "is_mandatory": true
+ }]
+ ...
+ ...
+}
+```
+
+> Example for Conditions (resource name)
+
+```shell
+{
+ ...
+ ...
+ "conditions": [{
+ "field":"resource",
+ "operator":"match",
+ "values":[3,5,8],
+ "weightage":10,
+ "is_mandatory": true
+ }]
+ ...
+ ...
+}
+```
+
+> Example for Conditions (resource start date)
+
+```shell
+{
+ ...
+ ...
+ "conditions": [{
+ "field":"start_date",
+ "operator":"bt",
+ "values":["2023-03-24","2023-05-20"],
+ "weightage":10,
+ "is_mandatory": true
+ }]
+ ...
+ ...
+}
+```
+
+
+> Example for Conditions (resource last date)
+
+```shell
+{
+ ...
+ ...
+ "conditions": [{
+ "field":"last_date",
+ "operator":"eq",
+ "values":"2023-03-24",
+ "weightage":20,
+ "is_mandatory": true
+ }]
+ ...
+ ...
+}
+```
+
+
+> Example for Conditions (time zone)
+
+```shell
+{
+ ...
+ ...
+ "conditions": [{
+ "field":"timezone",
+ "operator":"any",
+ "values":[315,240],
+ "weightage":10,
+ "is_mandatory": true
+ }]
+ ...
+ ...
+}
+```
+
+> Example for Conditions (resource primary_role)
+
+```shell
+{
+ ...
+ ...
+ "conditions": [{
+ "field":"primary_role_id",
+ "weightage":10
+ }]
+ ...
+ ...
+}
+```
+
+> Example for Conditions (resource availability)
+
+```shell
+{
+ ...
+ ...
+ "conditions": [{
+ "field":"availability",
+ "weightage":10
+ }]
+ ...
+ ...
+}
+```
+
+### Conditions for System Generated Fields
+
+|**Field code** | | **Operators**
+|:--|:--|:--
+**resource_type_id**||
**eq** (_default_)
any
+**resource**||
**match** (_default_)
+**start_Date**||
**eq** (_default_)
lt
gt
bt
ex
+**last_date**||
**eq** (_default_)
lt
gt
bt
ex
|
+**timezone**||
**eq** (_default_)
any
+**primary_role_id**||N/A
+**availability**||N/A
+
+### Conditions for User Generated Fields
+
+|**Field Type**| |**Operators**
+|:--|:--|:--
+|**Integer Number**||
**eq** *(default)*
lt
gt
bt
ex
+|**Fractional Number**||
**eq** *(default)*
lt
gt
bt
ex
+|**Date**||
**eq** *(default)*
lt
gt
bt
ex
+|**Checkbox**|| N/A
+|**Checkbox Group**||
**any** *(default)*
all
+|**Radio Group**||
**eq** *(default)*
any
+|**Label**||
**eq** *(default)*
any
+|**Drop Down Single Select**||
**eq** *(default)*
any
+|**Drop Down Multi Select**||
**any** *(default)*
all
+|**User Single Select**||
**eq** *(default)*
any
+|**User Multi Select**||
**any** *(default)*
all
+
+
+
+
+## Delete a Requirement
+
+Permanently deletes a requirement. It cannot be undone.
+
+> **`DELETE /v1/requirements/{ID}`**
+
+> Example Request
+
+```shell
+curl -v -X DELETE "https://app.eresourcescheduler.cloud/rest\
+/v1/requirements/1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+
+> Example Request: Delete requirement and its linked bookings
+
+```shell
+curl -v -X DELETE "https://app.eresourcescheduler.cloud/rest/v1\
+/requirements/106?delete_bookings=true" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Request: Delete requirement and unlinking its linked bookings
+
+```shell
+curl -v -X DELETE "https://app.eresourcescheduler.cloud/rest/v1\
+/requirements/106?unlink_bookings=true" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+### Returns
+
+
+| Code | Description
+| ---: | :----
+**200** `OK` | This status code indicates that the operation was successful and a requirement deleted successfully.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested requirement does not exist or has been deleted already.
+**409** `Conflict` | Conflict indicates that when you are deleting a requirement linked to booking(s), then you must pass one of the parameters i.e; `delete_bookings=true` to delete both requirement and respective booking or another parameter `unlink_bookings=true` will delete requirement after unlinking the respective bookings. this action will be performed through Administrator Requirement Settings.
diff --git a/source/includes/_requirementprofile.md b/source/includes/_requirementprofile.md
new file mode 100644
index 00000000000..48d28967110
--- /dev/null
+++ b/source/includes/_requirementprofile.md
@@ -0,0 +1,138 @@
+
+# Requirement Profile
+
+## Requirement Profile Object
+
+Requirement profile object represents requirement profile.
+
+> **`/v1/requirement/fields`**
+
+> Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/requirement/fields" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Response
+
+```json
+{
+ "id": 29,
+ "code": "effort",
+ "display_name": "Effort",
+ "field_type": "EFFORT",
+ "minnum": 0,
+ "is_system_defined":true,
+ "is_required": true
+},
+{
+ "id": 17,
+ "code": "end_time",
+ "display_name": "Ends",
+ "field_type": "DATIM",
+ "is_required": true,
+ "is_system_defined": true,
+ "maxdate": "2099-12-31",
+ "mindate": "1900-01-01"
+},
+{
+ "id": 31,
+ "code": "role_id",
+ "display_name": "Performing Role",
+ "field_type": "ROLEPS",
+ "is_required": false,
+ "is_system_defined": true,
+ "options": [
+ {
+ "id":6,
+ "name":"Accountant",
+ "description": null
+ },
+ {
+ "id":7,
+ "name":"Business Analyst",
+ "description":null},
+ {
+ "id":4,
+ "name":"Consultant",
+ "description":null},
+ {
+ "id":5,
+ "name":"Project Manager",
+ "description":null},
+ {
+ "id":3,
+ "name":"Tax Manager",
+ "description":null}
+ ]
+},
+{
+ "id": 3,
+ "code": "project_id",
+ "display_name": "Project",
+ "field_type": "PRJSS",
+ "is_required": true,
+ "is_system_defined": true
+},
+{
+ "id": 16,
+ "code": "start_time",
+ "display_name": "Starts",
+ "field_type": "DATIM",
+ "is_required": true,
+ "is_system_defined": true,
+ "maxdate": "2099-12-31",
+ "mindate": "1900-01-01"
+},
+{
+ "id": 32,
+ "code": "tags",
+ "display_name": "Tags",
+ "field_type": "TAGS",
+ "is_required": false,
+ "is_system_defined": true
+},
+{
+ "id": 30,
+ "code": "task_id",
+ "display_name": "Task",
+ "field_type": "TSKSS",
+ "is_required": false,
+ "is_system_defined": true
+},
+{
+ "id": 5,
+ "code": "unit",
+ "display_name": "Unit",
+ "field_type": "UNIT",
+ "minnum": 1,
+ "is_required": false,
+ "is_system_defined": true
+}
+
+```
+
+
+
+ATTRIBUTES
+
+Name | Description
+| ---: | :---- |
+**id** `integer` | Represents unique identification number of this field, which can be used to refer or search it.
+**code** `string` | It represents the unique code of the field which is referred as API code. This code acts as `key` in API response and the same must be used as `key` to pass values for a POST or PUT request.
+**field_type** `string` | Represents the type of field. For example TEXT (for Text Field), INT (for Integer Number field), DDSS (for Dropdown Single Select Field), etc.See User Defined Fields to know more about different field types.
+**display_name** `string` |Name of this field to identify it.
+**is_system_defined** `boolean` | Indicates whether this field is system defined or a custom field. Fields which are system defined can not be customized.
+**is_required** `boolean` |Indicates whether this field is mandatory or not. If this field is a required field then a valid value for this field must be passed while creating such object and while updating object (if this field is intended to update).
+**regex** `string` | Represents regular expression which must be matched by value for this field. Only applicable for text fields.
+**fields.minlength** `integer` | Represents minimum no of characters in value this field can accept. Only applicable for text fields.
+**fields.maxlength** `integer` | Represents maximum no of characters in value this field can accept. Only applicable for text fields.
+**minnum** `integer` | Represents minimum value this field can accept. Only applicable for numeric fields.
+**maxnum** `integer` | Represents maximum value this field can accept. Only applicable for numeric fields.
+**mindate** `string` |Represents minimum value this field can accept. Only applicable for date / date time fields.
+**maxdate** `string` |Represents maximum value this field can accept. Only applicable for date / date time fields.
+**options** `array of objects` | Field types such as Dropdown Single Select, Dropdown Multi Select, Radio Group etc.
+**options.id** `integer` | Represents unique identification number for the individual option object.
+**options.name** `string` | Represents name or content of option object.
+**options.color** `string` | Allows a user to store color code of option object. Only applicable for LABEL type fields.
\ No newline at end of file
diff --git a/source/includes/_resource.md b/source/includes/_resource.md
new file mode 100644
index 00000000000..ff530e278fa
--- /dev/null
+++ b/source/includes/_resource.md
@@ -0,0 +1,1260 @@
+# Resource
+
+
+## Resource Object
+
+>Example Response
+
+```json
+{
+ "id": 1,
+ "first_name": "Andrew",
+ "last_name": "Mooney",
+ "name": "Andrew Mooney",
+ "type": {
+ "name": "Employee",
+ "description": null,
+ "id": 1,
+ "is_human": true
+ },
+ "email": "andrew@enbraun.com",
+ "start_date": "2018-01-01",
+ "last_date": null,
+ "image": "https://erscloud/img/7aca31f5-29ae205ba315",
+ "phone": null,
+ "roles": [{
+ "name": "Quality Engineer",
+ "description": null,
+ "id": 3
+ }, {
+ "name": "Business Analyst",
+ "description": null,
+ "id": 1
+ }],
+ "tags": [],
+ "disable_parallel_booking": false,
+ "timezone": {
+ "name": "(UTC+05:30) Asia/Calcutta (IST)",
+ "description": "Asia/Calcutta",
+ "id": 230
+ },
+ "created_on": "2018-08-20T09:22:02.728296Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2018-11-20T11:55:48.880898Z",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "udf_qualifications": [{
+ "name": "B.Tech Computers",
+ "description": null,
+ "id": 15
+ }, {
+ "name": "PMP",
+ "description": null,
+ "id": 13
+ }],
+ "udf_employee_no": "ABC0001",
+ "udf_office": {
+ "name": "New York",
+ "description": null,
+ "id": 10
+ },
+ "udf_department": {
+ "name": "Technical",
+ "description": null,
+ "id": 26
+ }
+}
+```
+
+`Resource` object represents resources (human / non-human) in your organization (i.e. Employees , Machines etc. ) which you want to schedule. Resources could be of multiple types with each type having it's own custom attributes along with system defined attributes. The API allows you to list, search, create, delete, and update resources.
+
+ATTRIBUTES
+
+Name | Description
+ ---: | :----
+**id** `integer` | Auto generated unique identifier for resource object.
+**first_name** `string` | First name of resource. This may be up to 100 characters.
+**last_name** `string` | Last name of resource. This may be up to 100 characters.
+**name** `string` | String value defining name of `non-human` type resource. This may be up to 100 characters.
+**type** `object` | Describes the type of resource. This is one of the type objects which an Administrator user creates using eRS Cloud Application.
+**email** `string` | Email address of resource object.
+**start_date** `string` | Represents the first working day of resource in organization. Resource does not have any availability before this date.
+**last_date** `string` | Represents the last working day of resource in organization. After this date, resource is considered archived and has no availability beyond this date.
+**image** `string`| String value representing URL of image file of resource.
+**phone** `string` | Phone number of the resource object.
+**roles** `array of objects` | List of role objects applied on this resource.
+**tags** `array of strings` | Tags are the list of strings (labels) attached to this resource object which could be used for the purpose of filtering, identification or other information.
+**timezone** `integer` | Defines and categorize resources based on their location. This field is only available when scheduling plus module is on.
+**disable_parallel_booking** `boolean` | Boolean value defining if resource can or cannot have multiple bookings at a time. Default value for disable parallel booking is false.
+**created_on** `string` | Timestamp at which this resource object was created.
+**created_by** `object` | Object representing user who created this resource object.
+**modified_on** `string` | Represents latest modification timestamp.
+**modified_by** `object` | Object representing most recent user who modified this resource object.
+**udf_\*** | Custom user-defined fields used to capture additional information of resource. User defined field can be of multiple types. Custom fields are very useful to configure resource objects to best fit requirements. In given example response, all keys starting with prefix `udf_` are user defined custom fields. Learn more
+
+
+
+## Create a Resource
+
+Creates a new resource object.
+
+> **`POST /v1/resources`**
+
+> Example Request For Human Type Of Resource:
+
+```shell
+ curl -v -X POST "https://app.eresourcescheduler.cloud/rest/v1/resources" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "first_name": "Andrew",
+ "last_name": "Mooney",
+ "resource_type_id": 1,
+ "start_date": "2018-01-01",
+ "email": "andrew@enbraun.com",
+ "roles" : [1,3],
+ "udf_employee_no": "ABC0001"
+ }'
+```
+
+> Example Request For Non-Human Type Of Resource:
+
+```shell
+ curl -v -X POST "https://app.eresourcescheduler.cloud/rest/v1/resources" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "name": "Projector EX4300",
+ "start_date": "2018-06-01",
+ "resource_type_id": 2,
+ "udf_battery_capacity": 4
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+ ---: | :----
+**resource_type_id** `required` | ID of resource-type object. Every resource must be linked to a resource-type. Let’s assume there are two resource types defined as Employee (_having ID 1_) and Meeting Room (_having ID 2_). While creating a new resource, all the resource whose `resource_type_id` is given as **1** will get created under Employee type and the same for Meeting Room when `resource_type_id` is **2**.
+**first_name** `required` | String representing the first name of a resource. This may be up to 100 characters. _**Note**: for `non-human` resources, this field is not available_.
+**last_name** ⚑⚑ | String representing the last name of a resource. This may be up to 100 characters. _**Note**: for `non-human` resources, this field is not available_.
+**name** `required` | String representing the name of a resource. This may be up to 100 characters. _**Note**: This field is only available for `non-human` resources, and for `human` resources, this field is not available_.
+**start_date** `required` | String value representing a date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. A resource is only available from it's start date i.e system does not consider any capacity of resource before this date.
+**last_date** `optional` | String value representing a date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. A resource is only available till it's last working date i.e system does not consider any capacity of resource beyond this date (_if defined_).
+**email** ⚑⚑ | String value representing email address of resource object. Email address must be properly formatted with a maximum length of 254 characters.
+**phone** ⚑⚑ | String representing phone number of resource. It’s displayed alongside the resource in your resource list.
+**roles** ⚑⚑ | An array of IDs of Roles (which are defined by an Administrator user in eRS Cloud Application) to be assigned to this Resource. The first ID in the array is considered as Primary Role of that Resource. Multiple performing roles can be applied to a resource. Resources can also be searched / filtered using performing roles.
+**calendar** `optional` | ID of Calendar object which should be assigned to resource effective from it's `start_date`. Depending upon requirements, different calendars can be applied on different resources. If calendar is omitted then default calendar (as defined in Administrator calendar settings) will be applied for this resource.
+**tags** ⚑ | An optional array of strings which could be attached to this resource object as labels. This can be useful for the purpose of filtering, identification or other information.
+**timezone** ⚑⚑ | One timezone object can be defined for a resource.
_**Note**: This field is only available when scheduling plus module is on._
+**disable_parallel_booking** `optional` | Boolean value defining if resource can or cannot have multiple bookings at a time. Default value for disable parallel booking is false.
+**udf_\*** ⚑⚑ | A user with Administrator rights can add custom fields. These fields can be used to capture additional information in Resources. Different types of resources may have a different set of user-defined fields. The value for user defined field can be passed as shown in example request. In first example `udf_employee_no` is a user defined field. Learn more
_**Note**: User with Administrator rights can make fields marked with ⚑ mandatory and remove fields marked with ⚑, from specific resource type using eRS Cloud Application. If mandatory fields are not passed with a valid value or removed fields are passed while creating resource, the operation will fail with response code **400**_.
+
+### Returns
+
+| Code | Description |
+| :--- | :---- |
+**201** `Created` | Indicates that the operation was successful and a resource created successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or has any unknown parameter. Additionally, Bad request may also occur in one of these conditions :
Resource's `start_date` is after it's `last_date`.
Trying to create resources more than subscribed no of resources.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+
+
+## List Resources
+
+Returns a list of resources. The resources are returned sorted by name.
+
+
+> **`GET /v1/resources`**
+
+
+> Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/resources" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+>Example Request With Offset And Limit
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/resources?offset=1&limit=15" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+
+> Example Response
+
+```json
+{
+ "total_count": 120,
+ "offset": 1,
+ "limit": 15,
+ "data": [{
+ "id": 1,
+ "first_name": "Andrew",
+ "last_name": "Mooney",
+ "name": "Andrew Mooney",
+ "type": {
+ "name": "Employee",
+ "description": null,
+ "id": 1,
+ "is_human": true
+ },
+ "email": "andrew@enbraun.com",
+ "start_date": "2018-01-01",
+ "last_date": null,
+ "image": "https://erscloud/img/7aca31f5-29ae205ba315",
+ "phone": null,
+ "roles": [{
+ "name": "Quality Engineer",
+ "description": null,
+ "id": 3
+ }, {
+ "name": "Business Analyst",
+ "description": null,
+ "id": 1
+ }],
+ "tags": [],
+ "disable_parallel_booking": false,
+ "timezone": {
+ "name": "(UTC+05:30) Asia/Calcutta (IST)",
+ "description": "Asia/Calcutta",
+ "id": 230
+ },
+ "created_on": "2018-08-20T09:22:02.728296Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2018-11-20T11:55:48.880898Z",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "udf_qualifications": [{
+ "name": "B.Tech Computers",
+ "description": null,
+ "id": 15
+ }, {
+ "name": "PMP",
+ "description": null,
+ "id": 13
+ }],
+ "udf_employee_no": "ABC0001",
+ "udf_office": {
+ "name": "New York",
+ "description": null,
+ "id": 10
+ },
+ "udf_department": {
+ "name": "Technical",
+ "description": null,
+ "id": 26
+ }
+ },
+ { ... },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`25`**. _Maximum value of `limit` can be_ **`500`**.
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**.
+
+
+
+### Returns
+
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and list of resources is returned.
+**400** `Bad Request` | Bad Request may occur when offset and limit value is negative integer.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+
+
+## Retrieve a Resource
+
+> **`GET /v1/resources/{ID}`**
+
+> Example Request
+
+```shell
+curl -v "https://app.eresourcescheduler.cloud/rest/v1/resources/1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "id": 1,
+ "first_name": "Andrew",
+ "last_name": "Mooney",
+ "name": "Andrew Mooney",
+ "type": {
+ "name": "Employee",
+ "description": null,
+ "id": 1,
+ "is_human": true
+ },
+ "email": "andrew@enbraun.com",
+ "start_date": "2018-01-01",
+ "last_date": null,
+ "image": "https://erscloud/img/7aca31f5-29ae205ba315",
+ "phone": null,
+ "roles": [{
+ "name": "Quality Engineer",
+ "description": null,
+ "id": 3
+ }, {
+ "name": "Business Analyst",
+ "description": null,
+ "id": 1
+ }],
+ "tags": [],
+ "disable_parallel_booking": false,
+ "timezone": {
+ "name": "(UTC+05:30) Asia/Calcutta (IST)",
+ "description": "Asia/Calcutta",
+ "id": 230
+ },
+ "created_on": "2018-08-20T09:22:02.728296Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2018-11-20T11:55:48.880898Z",
+ "modified_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "udf_qualifications": [{
+ "name": "B.Tech Computers",
+ "description": null,
+ "id": 15
+ }, {
+ "name": "PMP",
+ "description": null,
+ "id": 13
+ }],
+ "udf_employee_no": "ABC0001",
+ "udf_office": {
+ "name": "New York",
+ "description": null,
+ "id": 10
+ },
+ "udf_department": {
+ "name": "Technical",
+ "description": null,
+ "id": 26
+ }
+}
+```
+
+
+Retrieves the details of an existing resource. You only need to provide the unique resource identifier that was returned upon resource creation as request parameter.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and a resource is retrieved successfully.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested resource does not exist (i.e. There is no resource with given ID). This may also occur when requesting a resource that has been deleted.
+
+## Search Resources
+
+> **`POST /v1/resources/search`**
+
+> Example Request For Filter In JSON Format
+
+```shell
+curl -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/search" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "resource_type_id:eq": 1
+ }'
+```
+
+> Example Request For Filter By Passing Multiple Rules In JSON Format
+
+```shell
+curl -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/search?offset=1&limit=15" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "resource_type_id:eq": 1 ,
+ "roles:ex": [3,6]
+ }'
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`25`**. _Maximum value of `limit` can be_ **`500`**.
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**.
+
+
+Search Resource API allows filtering the results returned in various ways. This enables a great power to find out what is needed. eRS Cloud API also allows filtering on custom defined fields with multiple operators and conditions to cover up complex scenarios for searching.
+
+A filter condition consists of three components which are **_field_**, **_operator_** and **_value_**. For example, fetching only those resources having `resource_type_id` 1, could be achieved by adding `"resource_type_id:eq": 1` to your query. If operator is not supplied, it takes default operator for field. Read more
+
+Below is a list of available fields, which allow filtering resources:
+
+
+|**Field Code**| **Operator** | **Example**|
+|:--|:---|:--|
+**resource_type_id**|
| `"modified_on:eq": ["2021-07-08T00:00:00]` `"modified_on:lt": ["2021-07-08T00:00:00]` `"modified_on:gt": ["2021-07-08T59:59:59"]` `"modified_on:bt": ["2021-07-08T00:00:00", "2021-07-10T23:59:59"]` `"modified_on:bt": ["2021-07-08T00:00:00", ""]` `"modified_on:bt": ["", "2021-07-10T23:59:59"]` `"modified_on:ex": ["2021-07-08T00:00:00", "2021-07-10T23:59:59"]` `"modified_on:ex": ["2021-07-08T00:00:00", ""]` `"modified_on:ex": ["", "2021-07-10T23:59:59"]]`
+ _For filtering using custom fields and operators please check here._
+
+## Update a Resource
+
+Updates specified resource by setting the values of the parameters passed. Any parameters which are not provided remains unchanged. To unset existing value for a parameter, just pass an empty value i.e. `null`.
+
+This request accepts mostly the same arguments as `Create Resource` API, except user can never update `resource_type_id` of any resource.
+
+> **`PUT /v1/resources/{ID}`**
+
+> Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "email": "andrew@enbraun.com",
+ "roles" : [3,2],
+ "udf_employee_no": "ABC0003"
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+|Name | Description |
+| ---: | :---- |
+**first_name** `required` | String representing the first name of a resource. This may be up to 100 characters. _**Note**: for 'non-human' resources, this field is not available_.
+**last_name** ⚑⚑ | String representing the last name of a resource. This may be up to 100 characters. _**Note**: for `non-human` resources, this field is not available_.
+**name** `required` | String representing the name of a resource. This may be up to 100 characters. _**Note**: This field is only available for `non-human` resources, and for `human` resources, this field is not available_.
+**start_date** `required` | String value representing a date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. A resource is only available from it's start date i.e system does not consider any capacity of resource before this date.
+**last_date** `optional` | String value representing a date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. A resource is only available till it's last working date i.e system does not consider any capacity of resource beyond this date (_if defined_).
+**email** ⚑⚑ | String value representing email address of resource object. Email address must be properly formatted with a maximum length of 254 characters.
+**phone** ⚑⚑ | String representing phone number of resource. It’s displayed alongside the resource in your resource list.
+**roles** ⚑⚑ | An array of IDs of Roles (which are defined by an Administrator user in eRS Cloud Application) to be assigned to this Resource. The first ID in the array is considered as Primary Role of that Resource. Multiple performing roles can be applied to a resource. Resources can also be searched / filtered using performing roles.
+**tags** ⚑ | An optional array of strings which could be attached to this resource object as labels. This can be useful for the purpose of filtering, identification or other information.
+**timezone** ⚑⚑ | One timezone object can be defined for a resource.
_**Note**: This field is only available when scheduling plus module is on._
+**disable_parallel_booking** `optional` | Boolean value defining if resource can or cannot have multiple bookings at a time. Default value for disable parallel booking is false.
+**udf_\*** ⚑⚑ | A user with Administrator rights can add custom fields. These fields can be used to capture additional information in Resources. Different types of resources may have a different set of user-defined fields. The value for user defined field can be passed as shown in example request. In first example `udf_employee_no` is a user defined field. Learn more
_**Note**: User with Administrator rights can make fields marked with ⚑ mandatory and remove fields marked with ⚑, from specific resource type using eRS Cloud Application. If mandatory fields are not passed with a valid value or removed fields are passed while updating resource, the operation will fail with response code **400**_.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | Indicates that the operation was successful and requested resource updated successfully.|
+**400** `Bad Request` | Bad Request occurs when a request is not well-formed, syntactically incorrect, empty required parameters or any unknown parameter is passed. Additionally, Bad request may also occur in one of these conditions :
Trying to update an archived resource.
Trying to change `start_date` or `last_date` such that `last_date` gets smaller than `start_date`.
Trying to update `start_date` and `last_date` of a resource such that existing bookings of that resource do not fit in given range.
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested resource does not exist (i.e. There is no resource with given ID). This may also occur when updating a resource that has been deleted.
+
+
+## Delete a Resource
+
+ Permanently deletes requested resource. It cannot be undone. By default, this operation will fail if a resource has any bookings, timesheets or rates associated with it. To override this, forceful deletion can be used which will delete all bookings, timesheets and rates and then, ultimately deletes the resource object.
+
+> **`DELETE /v1/resources/{ID}`**
+
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+
+> Example Request For Forceful Delete
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/1/?\
+force_delete_bookings=true&force_delete_rates=true&\
+force_delete_timesheet_entry=true" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+### Returns
+
+
+| Code | Description
+| ---: | :----
+**200** `OK` | This status code indicates that the operation was successful and a resource deleted successfully.
+**409** `Conflict` | Conflict indicates that the resource can not be deleted because there are bookings, timesheets or rates associated with this resource. If you wish to delete it anyway, you must use force delete option by passing `true` for parameters `force_delete_bookings`, `force_delete_timesheet_entry` and `force_delete_rates` which will delete associated bookings, timesheets and rates corresponding to the resource. This operation deletes all bookings, timesheets and rates of requested resource and resource itself (shown in example request).
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | Not Found error occurs when requested resource does not exist.
+
+## Timings
+
+> Example Response
+
+```json
+ {
+ "id": 5,
+ "name": "Part Time",
+ "effective_date": "2018-11-15",
+ "applied_on": "2018-11-03T15:06:15.454+05:30",
+ "created_on": "2018-11-03T15:06:15.484913+05:30",
+ "modified_on": null,
+ "created_by": {
+ "id": 2,
+ "name": "Patrick Wilson"
+ },
+ "modified_by": {
+ "id": null,
+ "name": null
+ },
+ "timings": [
+ {
+ "day_num": 2,
+ "start_time": 600,
+ "end_time": 840
+ }
+ ]
+
+ }
+```
+
+To capture timings about a resource, eRS Cloud provides Timings. One resource may work in different timings as per his availability or requirement, for such situations Timings are beneficial.
+
+Let say, If a resource works on a full-time profile but then for a certain period of time he switched his timings from full-time to part-time. Then for that certain period part-time calendar will be applied along with it's effective date. Timings are beneficial to apply multiple calendars on a resource.
+
+eRS Cloud API allows you to perform *`POST`*, *`GET`*, *`PUT`*, *`DELETE`* operations on Timings.
+
+ATTRIBUTES
+
+Name | Description
+ ---: | :----
+ **id** `integer` | eRS Cloud generated unique identifier for the calendar object. |
+ **name** `string` | This field describes name of calendar object. |
+ **effective_date** `string` | Effective date is the date on which the calendar will come into effect on applied resources.
+ **applied_on** `string` |This field describes when calendar is applied.
+ **created_on** `string` | Time at which the calendar object is created.
+ **created_by** `object` | This field describes by whom calendar object is created.|
+ **modified_on** `string` | Timestamp of the latest modification.
+ **modified_by** `object` | This field describes by whom the latest modification is done.
+ **timings** `array of strings` | Timings are list of days in which `day_num` is defined day(For example-0 for sunday,1 for monday) and `start_time` and `end_time` are defined as start time and end time for a particular day respectively, also we can calculate no of working-hours on that day.|
+ **timings.day_num** `integer` | Represents day of week, starting from 0 (for Sunday) to 6 (for Saturday). |
+ **timings.start_time** `integer` | Represents start time for this timing block in minutes (since 12 AM) i.e. for 6:00 AM, value would be 6 * 60 = 360 and for 9:00 AM it would be 9 * 60 = 540. |
+ **timings.end_time** `integer` | Represents end time for this timing block in minutes (since 12 AM) i.e. for 5:00 PM, value would be (12+5) * 60 = 1020. |
+
+
+
+### Retrieving the timings
+
+> `GET v1/resources/{ID}/timings`
+
+> Example Request
+
+```shell
+curl -v -X GET "https://app.eresourcescheduler.cloud/rest/v1/resources/12/timings"\
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+
+```json
+{
+ "total_count": 3,
+ "data": [
+ {
+ "id": 5,
+ "name": "Part Time",
+ "effective_date": "2018-11-15",
+ "applied_on": "2018-11-03T15:06:15.454+05:30",
+ "created_on": "2018-11-03T15:06:15.484913+05:30",
+ "modified_on": null,
+ "created_by": {
+ "id": 2,
+ "name": "Patrick Wilson"
+ },
+ "modified_by": {
+ "id": null,
+ "name": null
+ },
+ "timings": [
+ {
+ "day_num": 2,
+ "start_time": 600,
+ "end_time": 840
+ },
+ {...},
+ {...},
+ ]
+ },
+ {...},
+ {...}
+ ]
+}
+```
+
+Retrieves the details of timings which are applied to the resource. You only need to provide the unique resource identifier that was returned upon resource creation.
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This status code indicates that the operation was successful and timings retrieved successfully . |
+| **403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | Not Found error occurs when requested resource does not exist (i.e. There is no resource with given ID). This may also occur when requesting a resource that has been deleted. |
+
+
+
+
+### Applying new timing
+
+> `POST v1/resources/{ID}/timings`
+
+> Example Request
+
+```shell
+curl -v -X POST "https://app.eresourcescheduler.cloud/rest/v1/resources/12/timings" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "applied_on": "2018-12-04T08:14:41.109Z",
+ "calendar_id": "5",
+ "effective_date": "2018-02-02"
+ }'
+```
+> Example request to replace existing calendar
+
+```shell
+curl -v -X POST "https://app.eresourcescheduler.cloud/rest/v1/resources/12/timings" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "applied_on": "2018-12-04T08:14:41.109Z",
+ "calendar_id": "1",
+ "effective_date": "2018-02-02"
+ "replace_existing_date": true
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+ ---: | :----
+**applied_on** `required`| Applied on Field describes when calendar is applied. It is a `DateTime` type of field.
+**calendar_id** `required`|As the name shows it is a calendar ID which we have to pass. You will get this ID at the time of calendar creation. This field accepts `Integer` only.
+**effective_date** `required`|Effective date is the date on which the calendar will come into effect on applied resources. This field accepts `Date` only.
+
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+| **201** `Created` | This status code indicates that the operation was successful and timings applied successfully.|
+| **400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters are or any unknown parameter is passed. |
+| **403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | Not Found error occurs when requested resource does not exist.
+| **409** `Conflict` | Conflict status indicates that the calendar cannot be applied on the provided effective date because a calendar is already set for that date. If you still wish to apply it on the same date, you must use the "replace existing" option by setting the `replace_existing_date` parameter to `true`. This will replace the existing calendar with the new one. Example request is shown to right.
+
+
+### Update timings
+
+
+> `PUT v1/resources/{ID}/timings/{Timing_ID}`
+
+> Example Request
+
+```shell
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest/v1/resources/12/timings/2" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "applied_on": "2018-12-04T08:14:41.109Z",
+ "calendar_id": "5",
+ "effective_date": "2018-02-02"
+ }'
+```
+
+
+
+Updates the specified resource's calendar by setting the value of the parameter passed. You need to provide the unique resource identifier that was returned upon resource creation and unique timing identifier that was returned upon timing addition. If parameter is not provided then it will be left unchanged.
+
+This request accepts mostly the same argument as the note creation call.
+
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+ ---: | :----
+**applied_on** `required`| Applied on Field describes when calendar is applied. It is a `DateTime` type of field.
+**calendar_id** `required`|As the name shows it is a calendar ID which we have to pass. You will get this ID at the time of calendar creation. This field accepts `Integer` only.
+**effective_date** `required`|Effective date is the date on which the calendar will come into effect on applied resources. This field accepts `Date`only.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This indicates that the operation was successful and timings updated successfully.|
+| **400** `Bad Request` | Bad Request occurs when a request is not well-formed, syntactically incorrect, empty required parameters or any unknown parameter is passed. Bad request can also occur when when trying to update timing as there will be no effective timing on `start_date` of resource.|
+| **403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | Not Found error occurs when requested resource ID or timing ID does not exist.
+
+### Delete timings
+
+
+> `DELETE v1/resources/{ID}/timings/{Timing_ID}`
+
+Permanently deletes a applied Calendar. It cannot be undone. You need to provide the unique resource identifier that was returned upon resource creation and unique timing identifier that was returned upon timing addition.
+
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/12/timings/2" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+### Returns
+
+| Code | Description
+| ---: | :----
+| **200** `OK` |This status code indicates that the operation was successful and an applied calendar deleted successfully. |
+| **400** `Bad Request` | Bad request indicates that this timing cannot be deleted from this resource as this calendar is effective from or before `start_date` of resource.
+| **404** `Not Found` | Not Found error occurs when requested resource ID or timing ID does not exist.
+
+## Exceptions
+
+>Example Response
+
+```json
+{
+ "total_count":1,
+ "data":[
+ {
+ "id":2,
+ "name":"Working Sunday",
+ "description":"Working Sunday",
+ "date":"2018-11-17",
+ "is_working_exception":true,
+ "created_on":"2018-11-03T15:07:30.917087+05:30",
+ "modified_on":null,
+ "created_by":{
+ "id":2,
+ "name":"Patrick Wilson"
+ },
+ "modified_by":{
+ "id":null,
+ "name":null
+ },
+ "timings":[
+ {
+ "start_time":600,
+ "end_time":1080
+ }
+ ]
+ }
+ ]
+}
+```
+
+Exception is nothing but time duration that is different from a general schedule. eRS provides you the feature to add an exception to a resource.
+
+Let's say, a resource having calendar which does not have Sunday working. But for some reason, resource has to work on Sunday then this is a case of exception. So in such a situation exception comes handy.
+
+eRS Cloud provides you two types of exceptions:
+
Working Exception :
Working Exception is added on a non-working day.
Non-working Exception :
Non-working Exception is added on a working day.
+
+_**Note**: Working Exception can be added without timings._
+
+ATTRIBUTES
+
+Name | Description
+ ---: | :----
+ **id** `integer` | eRS Cloud generated unique identifier for the exceptions object.|
+ **name** `string` | This field describes name of exception.|
+ **description** `string` | This field describes about the exception.|
+ **date** `string` | Date Field describes when will the exception get applied.|
+ **is_working_exception** `boolean`|Is working exception describes whether exception is a working exception or non working exception. True value means that exception is working exception and false value means that exception is non working exception.
+ **created_on** `string` | Time at which exception is created. |
+ **modified_on** `string` | Timestamp of the latest modification. |
+ **created_by** `object` | This field describes by whom exception is created .|
+ **modified_by** `object` | This field describes by whom the latest modification is done. |
+ **timings** `object` |Timings describe the timings of exception.
+
+
+
+### Retrieving exceptions
+
+> `GET v1/resources/{ID}/exceptions`
+
+> Example Request
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/12/exceptions" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "total_count":1,
+ "data":[
+ {
+ "id":2,
+ "name":"Working Sunday",
+ "description":"Working Sunday",
+ "date":"2018-11-17",
+ "is_working_exception":true,
+ "created_on":"2018-11-03T15:07:30.917087+05:30",
+ "modified_on":null,
+ "created_by":{
+ "id":2,
+ "name":"Patrick Wilson"
+ },
+ "modified_by":{
+ "id":null,
+ "name":null
+ },
+ "timings":[
+ {
+ "start_time":600,
+ "end_time":1080
+ }
+ ]
+ }
+ ]
+}
+```
+
+Retrieves the details of exceptions which are applied to the resource. You only need to provide the unique resource identifier that was returned upon resource creation.
+
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This status code indicates that the operation was successful and exceptions retrieved successfully. |
+| **403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | Not Found error occurs when requested resource does not exist (i.e. There is no resource with given ID). This may also occur when requesting a resource that has been deleted. |
+
+
+### Create an exception
+
+> `POST v1/resources/{ID}/exceptions`
+
+> Example Request
+
+```shell
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/12/exceptions" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "date": "2018-11-02",
+ "description": "Thursday 1",
+ "name": "Thursday 1",
+ "is_working_exception": true,
+ "timing_blocks":[
+ {
+ "start_time":600,
+ "end_time":1080
+ }
+ ]
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**date** `required`| Date Field describes when will the exception get applied. It is a `Date` type of field.
+**description** `optional`|As the name shows it is a description which we want to give for the exception . This field is a `string` type of field.
+**name** `required`|Name describes the name of exception. This field is a `string` type of field.
+**is_working_exception** `required`|Is working exception describes whether exception is a working exception or not. Accepts `true` if it is a working exception otherwise accepts `false` if it a non-working exception. This field is a `boolean` type of field.
+**timing_blocks** `optional`|Timing blocks describes the timings of exception. This field can be passed `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Array of objects` type of field.
+**timing_blocks.start_time** `optional`|Start time describes the start time of exception. This field can be passed `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Integer` type of field.
+**timing_blocks.end_time** `optional`|End time describes the end time of exception. This field can be passed `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Integer` type of field.
+
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+| **201** `Created` | This status code indicates that the operation was successful and exception created successfully.|
+| **400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters are or any unknown parameter is passed. |
+| **403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` |This status code indicates that resource does not exist.|
+### Update an exception
+
+
+> `PUT v1/resources/{ID}/exceptions/{Exception_ID}`
+
+> Example Request
+
+```shell
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/12/exceptions/2" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "date": "2018-11-02",
+ "description": "Thursday 1",
+ "name": "Thursday 1",
+ "is_working_exception": true,
+ "timing_blocks":[
+ {
+ "start_time":600,
+ "end_time":1080
+ }
+ ]
+ }'
+```
+
+
+
+Updates the specified resource's exception by setting the value of the parameter passed. You need to provide the unique resource identifier that was returned upon resource creation and unique exception identifier that was returned upon exception addition. If parameter is not provided then it will be left unchanged.
+
+This request accepts mostly the same argument as the exception creation call.
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+ ---: | :----
+**date** `required`| Date Field describes when will the exception get applied. It is a `Date` type of field.
+**description** `optional`|As the name shows it is a description which we want to give for the exception . This field is a `string` type of field.
+**name** `required`|Name describes the name of exception. This field is a `string` type of field.
+**is_working_exception** `required`|Is working exception describes whether exception is working exception or not. Accepts `true` if it is working exception otherwise accepts `false` if it a non-working exception. This field is a `boolean` type of field
+**timing_blocks** `optional`|Timing blocks describes the timings of exception. This field can be pass `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Array of objects` type of field.
+**timing_blocks.start_time** `optional`|Start time describes the start time of exception. This field can be pass `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Integer` type of field.
+**timing_blocks.end_time** `optional`|End time describes the end time of exception. This field can be pass `null`, as eRS Cloud provides you the facility to create an exception without timings. This field is a `Integer` type of field.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This indicates that the operation was successful and a exception updated successfully.|
+| **400** `Bad Request` | Bad Request occurs when a request is not well-formed, syntactically incorrect, empty required parameters or any unknown parameter is passed.|
+| **403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` |This status code indicates that resource or exception does not exist.|
+
+
+### Delete an exception
+
+> `DELETE v1/resources/{ID}/exceptions/{Exception_ID}`
+
+Permanently deletes an applied exception. It cannot be undone. You need to provide the unique resource identifier that was returned upon resource creation and unique exception identifier that was returned upon exception addition.
+
+
+> Example Request
+
+```shell
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/12/exceptions/2"\
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+
+
+| Code | Description
+| ---: | :----
+| **200** `OK` |This status code indicates that the operation was successful and exception deleted successfully. |
+| **404** `Not Found` |This status code indicates that resource or exception does not exist.|
+
+## Notes
+
+> Example Response
+
+```json
+{
+ "total_count":3,
+ "limit":25,
+ "offset":0,
+ "data":[
+ {
+ "id":8,
+ "created_on":"2018-09-02T17:41:14.642026+05:30",
+ "content":"
Awarded by "Employee Of The Month"
+ award on Aug 09, 2017
",
+ "modified_on":null,
+ "created_by":{
+ "id":2,
+ "name":"Patrick Wilson"
+ },
+ "modified_by":{
+ "id":null,
+ "name":null
+ }
+ },
+ {...},
+ {...}
+ ]
+}
+```
+
+To capture additional information about a resource, eRS Cloud provides the `Notes`. If one has to provide any new information to a resource that is not captured from the field, for such situations Notes are beneficial.
+
+Let's say, If a resource has role "A", but after a certain time his role changed or new role gets added to his profile. Roles field gives us the ability to add, update or delete a role. But it does not give brief information when the role added, deleted or updated. The Notes comes in handy in such situations. Notes are handy to maintain the history of a resource.
+
+eRS Cloud API allows you to perform *`POST`*, *`GET`*, *`PUT`*, *`DELETE`* operations on Notes.
+
+_**Note**: The Notes Of Archived Resource remain available for the records._
+
+ATTRIBUTES
+
+Name | Description
+ ---: | :----
+ **id** `integer` | eRS Cloud generated unique identifier for the notes. |
+ **content** `string` | Text written inside notes body.|
+ **created_on** `string` | Time at which the notes object is created. |
+ **modified_on** `string` | Timestamp of the latest modification.|
+ **created_by** `object` | This field describes by whom this note is created.|
+ **modified_by** `object` | This field describes by whom the latest modification is done .
+
+### List notes
+
+>` GET v1/resources/{ID}/notes`
+
+
+Retrieves the Notes list of specified resource. You need to provide the unique resource identifier that was returned upon resource creation. The notes are returned which are sorted by lastly modified or added.
+
+> Example Request
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/8/notes" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+>Example Request With Offset And Limit
+
+```shell
+curl -v -X GET \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/8/notes?offset=1&limit=10" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+>Example Request With order_by
+
+```shell
+curl -v -X GET \
+ "https://app.eresourcescheduler.cloud/rest/v1/resources/8/notes?offset=1&limit=10&order_by=created_on" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Response
+
+```json
+{
+ "total_count":3,
+ "limit":10,
+ "offset":1,
+ "data":[
+ {
+ "id":8,
+ "created_on":"2018-09-02T17:41:14.642026+05:30",
+ "content":"
Awarded by "Employee Of The Month"
+ award on Aug 09, 2017
",
+ "modified_on":null,
+ "created_by":{
+ "id":2,
+ "name":"Patrick Wilson"
+ },
+ "modified_by":{
+ "id":null,
+ "name":null
+ }
+ },
+ {...},
+ {...}
+ ]
+}
+```
+
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+|**limit** `optional`|The limit keyword is used to limit the number of notes returned from a result set. *The default value of limit is* *`25`.* *Maximum value of limit can be* *`100.`* *If Limit value is exceeds than**`100`* *then it will set to* *`100`* *which is Maximum value for limit.* |
+|**offset** `optional`|The Offset value allows specifying which note to start from retrieving data. The Offset value is also most often used together with the Limit keyword. *The default value of offset is* *`0`.* |
+
+
+### Ordering The Notes
+
+REQUEST QUERY PARAMETERS
+
+|Name|Options|Description|
+|-:|:-:|:-
+|**order_by** `optional`|
**created_on** *(Default)*
|List of notes will be returned and sorted by it's created date.|
+| |
modified_on
|List of notes will be returned and sorted by it's latest modified date.|
+
+
+### Returns
+
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This indicates that the operation was successful and a list of notes is returned. |
+**400** `Bad Request` | Bad Request may occur when offset and limit value is given as negative integer. |
+**403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+**404** `Not Found` |This status code indicates that resource does not exist.|
+
+
+### Create a note
+
+>` POST v1/resources/{ID}/notes`
+
+
+> Example Request
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/8/notes"\
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"\
+ -H "Content-Type: application/json"\
+ -d '{"content": "Hello Enbraun"}'
+```
+
+> Example Request With HTML Tag
+
+```shell
+
+curl -v -X POST \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/8/notes" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{"content": "
Hello Enbraun
"}'
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+ ---: | :----
+ **content** `required` | To create new note you have to pass the body from `content` parameter. Content param accepts plain text. Also, you can pass text with HTML tags as Notes are Multi Line Rich Text.
+
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+| **201** `Created` | This status code indicates that the operation was successful and created a note successfully.|
+| **400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameters are passed. |
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | This status code indicates that resource does not exist.|
+
+
+
+
+### Update a note
+
+>` PUT v1/resources/{ID}/notes/{Note_ID}`
+
+Updates the specified resource's note by setting the value of the parameter passed. You need to provide the unique resource identifier that was returned upon resource creation and unique note identifier that was returned upon note's creation. If parameter is not provided then it will be left unchanged.
+
+This request accepts mostly the same argument as the note creation call.
+
+> Example Request
+
+```shell
+
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/8/notes/4" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{"content": "Hello World"}'
+```
+
+> Example Request With HTML Tag.
+
+```shell
+
+curl -v -X PUT \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/8/notes/4" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"\
+ -H "Content-Type: application/json" \
+ -d '{"content": "
Hello World
"}'
+```
+
+REQUEST BODY PARAMETERS
+
+
+Name | Description
+ ---: | :----
+ **content** `required` | To update note you have to pass the body from `content` parameter. Content param accepts plain text. Also, you can pass text with HTML tags as Notes are Multi Line Rich Text.
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This indicates that the operation was successful and a note updated successfully.|
+| **400** `Bad Request` | Bad Request occurs when a request is not well-formed, syntactically incorrect, empty required parameters or any unknown parameters are passed.|
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | This status code indicates that resource or note does not exist.|
+
+
+### Delete a note
+
+>` DELETE v1/resources/{ID}/notes/{Note_ID}`
+
+Permanently deletes a Note. It cannot be undone. You need to provide the unique resource identifier that was returned upon resource creation and unique note identifier that was returned upon note's creation.
+
+> Example Request
+
+```shell
+
+curl -v -X DELETE \
+"https://app.eresourcescheduler.cloud/rest/v1/resources/8/notes/5" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+
+
+| Code | Description
+| ---: | :----
+| **200** `OK` | This status code indicates that the operation was successful and a note deleted successfully. |
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | This status code indicates that resource or note does not exist.|
diff --git a/source/includes/_resourcetypes.md b/source/includes/_resourcetypes.md
new file mode 100644
index 00000000000..99527c30c73
--- /dev/null
+++ b/source/includes/_resourcetypes.md
@@ -0,0 +1,450 @@
+# Resource Types
+
+## Resource Type Object
+
+> Example Response
+
+```json
+{
+ "id": 1,
+ "name": "Employee",
+ "description": "",
+ "is_human": true,
+ "color": "#000000;1",
+ "fields": [{
+ "id": 52,
+ "code": "udf_department",
+ "display_name": "Department",
+ "field_type": "DDSS",
+ "is_required": false,
+ "is_system_defined": false,
+ "options": [{
+ "id": 27,
+ "name": "Service",
+ "description": null
+ },
+ {
+ "id": 26,
+ "name": "Technical",
+ "description": null
+ },
+ { ... }
+ ]
+ }, {
+ "id": 11,
+ "code": "email",
+ "display_name": "Email",
+ "field_type": "EMAIL",
+ "placeholder_text": "Enter valid email id",
+ "maxlength": 254,
+ "regex": "^[a-zA-Z]+[a-zA-Z0-9._]+@[a-zA-Z]+\\.[a-zA-Z.]{2,5}$",
+ "is_required": false,
+ "is_system_defined": true
+ }, {
+ "id": 46,
+ "code": "udf_employee_no",
+ "display_name": "Employee No.",
+ "field_type": "TEXT",
+ "minlength": 1,
+ "maxlength": 10,
+ "is_required": false,
+ "is_system_defined": false
+ }, {
+ "id": 7,
+ "code": "first_name",
+ "display_name": "First Name",
+ "field_type": "TEXT",
+ "help_text": "",
+ "placeholder_text": "Enter first name",
+ "minlength": 1,
+ "maxlength": 100,
+ "is_required": true,
+ "is_system_defined": true
+ }, {
+ "id": 8,
+ "code": "last_name",
+ "display_name": "Last Name",
+ "field_type": "TEXT",
+ "placeholder_text": "Enter last name",
+ "maxlength": 100,
+ "is_required": false,
+ "is_system_defined": true
+ }, {
+ "id": 14,
+ "code": "last_date",
+ "display_name": "Last Working Date",
+ "field_type": "DATE",
+ "is_required": false,
+ "is_system_defined": true,
+ "maxdate": "2099-12-31",
+ "mindate": "1900-01-01"
+ }, {
+ "id": 45,
+ "code": "udf_office",
+ "display_name": "Office",
+ "field_type": "DDSS",
+ "is_required": false,
+ "is_system_defined": false,
+ "options": [{
+ "id": 8,
+ "name": "Chicago",
+ "description": null
+ }, {
+ "id": 11,
+ "name": "Dallas",
+ "description": null
+ }, {
+ "id": 10,
+ "name": "New York",
+ "description": null
+ }, {
+ "id": 12,
+ "name": "San Francisco",
+ "description": null
+ }, {
+ "id": 9,
+ "name": "Washington",
+ "description": null
+ },
+ { ... }
+ ]
+ }, {
+ "id": 26,
+ "code": "phone",
+ "display_name": "Phone",
+ "field_type": "TEXT",
+ "maxlength": 50,
+ "is_required": false,
+ "is_system_defined": true
+ }, {
+ "id": 12,
+ "code": "start_date",
+ "display_name": "Start Date",
+ "field_type": "DATE",
+ "is_system_defined": true,
+ "maxdate": "2099-12-31",
+ "mindate": "1900-01-01",
+ "is_required": true
+ },
+ { ... }
+ ]
+}
+```
+
+Resource type object represents the type of resource. In an organization, there can be multiple types of resources. Administrator can add multiple resource types using eRS Cloud application. Resource types can be categorized as human or non-human. Human type of resource can be `Employee`, `Contractor`, etc. and non-human can be `Meeting Rooms`, `Projectors` etc. Different resource type objects can be configured to have a different sets of custom attributes as well, which allows customizing resource objects to fit your requirements.
+
+
+ATTRIBUTES
+
+Name | Description
+---------: | :-----------
+**id** `integer` | Unique identification number for the object, which allows referring to this object and can be used to search a particular resource type.
+**name** `string` | Represents name for this object. This is used to identify object by using some meaningful phrase to describe type of resources like `Employee`, `Machine` etc.
+**description** `string` | Description for the resource type object.
+**is_human** `boolean` | Indicates whether this resource type is `human` or `non-human`. For example, `Employee` could be a human resource type while `Machine`, `Meeting Rooms` etc. can be non-human resource type.
+**color** `string`| String representing the hexadecimal color code assigned to the resource type.
+**fields** `array of objects` | Represents collection of fields (or attributes) that are available for this resource type. Each Resource object of this resource type can store / update values for these field. While creating or updating a Resource user must pass arguments which are available for intended resource type object.
+**fields.id** `integer` | Represents unique identification number of this field, which can be used to refer or search it.
+**fields.display_name** `string` | Name of this field to identify it.
+**fields.field_type** `string` | Represents the type of field. For example TEXT (for Text Field), INT (for Integer Number field), DDSS (for Dropdown Single Select Field), etc. See User Defined Fields to know more about different field types.
+**fields.code** `string` | It represents the unique code of the field which is referred as API code. This code acts as `key` in API response and the same must be used as `key` to pass values for a POST or PUT request.
+**fields.minlength** `integer` | Represents minimum no of characters in value this field can accept. Only applicable for text fields.
+**fields.maxlength** `integer` | Represents maximum no of characters in value this field can accept. Only applicable for text fields.
+**fields.regex** `string` | Represents regular expression which must be matched by value for this field. Only applicable for text fields.
+**fields.minnum** `integer` | Represents minimum value this field can accept. Only applicable for numeric fields.
+**fields.maxnum** `integer` | Represents maximum value this field can accept. Only applicable for numeric fields.
+**fields.mindate** `string` | Represents minimum value this field can accept. Only applicable for date / date time fields.
+**fields.maxdate** `string` | Represents maximum value this field can accept. Only applicable for date / date time fields.
+**fields.is_required** `boolean` | Indicates whether this field is mandatory or not. If this field is a required field then a valid value for this field must be passed while creating such object and while updating object (if this field is intended to update).
+**is_system_defined** `boolean` | Indicates whether this field is system defined or a custom field. Fields which are system defined can not be customized.
+**fields.options** `array of objects` | Field types such as Dropdown Single Select, Dropdown Multi Select, Radio Group etc. ( See User Defined Fields to know more. ) Allows user to pick one or more from these available options.
+**fields.options.id** `integer` | Represents unique identification number for the individual option object.
+**fields.options.name** `string` | Represents name or content of option object.
+**fields.options.color** `string` | Allows a user to store color code of option object. Only applicable for LABEL type fields.
+
+
+
+## Get a Specific Resource Type
+
+Retrieves the details of an existing resource-type. You only need to provide the unique resource-type identifier of required resource-type.
+
+> **`GET /v1/resourcetypes/{ID}`**
+
+>Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/resourcetypes/1" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+>Example Response
+
+
+```json
+{
+ "id": 1,
+ "name": "Employee",
+ "description": "",
+ "is_human": true,
+ "color": "#000000;1",
+ "fields": [{
+ "id": 52,
+ "code": "udf_department",
+ "display_name": "Department",
+ "field_type": "DDSS",
+ "is_required": false,
+ "is_system_defined": false,
+ "options": [{
+ "id": 27,
+ "name": "Service",
+ "description": null
+ },
+ {
+ "id": 26,
+ "name": "Technical",
+ "description": null
+ },
+ { ... }
+ ]
+ }, {
+ "id": 11,
+ "code": "email",
+ "display_name": "Email",
+ "field_type": "EMAIL",
+ "placeholder_text": "Enter valid email id",
+ "maxlength": 254,
+ "regex": "^[a-zA-Z]+[a-zA-Z0-9._]+@[a-zA-Z]+\\.[a-zA-Z.]{2,5}$",
+ "is_required": false,
+ "is_system_defined": true
+ }, {
+ "id": 46,
+ "code": "udf_employee_no",
+ "display_name": "Employee No.",
+ "field_type": "TEXT",
+ "minlength": 1,
+ "maxlength": 10,
+ "is_required": false,
+ "is_system_defined": false
+ }, {
+ "id": 7,
+ "code": "first_name",
+ "display_name": "First Name",
+ "field_type": "TEXT",
+ "help_text": "",
+ "placeholder_text": "Enter first name",
+ "minlength": 1,
+ "maxlength": 100,
+ "is_required": true,
+ "is_system_defined": true
+ }, {
+ "id": 8,
+ "code": "last_name",
+ "display_name": "Last Name",
+ "field_type": "TEXT",
+ "placeholder_text": "Enter last name",
+ "maxlength": 100,
+ "is_required": false,
+ "is_system_defined": true
+ }, {
+ "id": 14,
+ "code": "last_date",
+ "display_name": "Last Working Date",
+ "field_type": "DATE",
+ "is_required": false,
+ "is_system_defined": true,
+ "maxdate": "2099-12-31",
+ "mindate": "1900-01-01"
+ }, {
+ "id": 45,
+ "code": "udf_office",
+ "display_name": "Office",
+ "field_type": "DDSS",
+ "is_required": false,
+ "is_system_defined": false,
+ "options": [{
+ "id": 8,
+ "name": "Chicago",
+ "description": null
+ }, {
+ "id": 11,
+ "name": "Dallas",
+ "description": null
+ }, {
+ "id": 10,
+ "name": "New York",
+ "description": null
+ }, {
+ "id": 12,
+ "name": "San Francisco",
+ "description": null
+ }, {
+ "id": 9,
+ "name": "Washington",
+ "description": null
+ },
+ { ... }
+ ]
+ }, {
+ "id": 26,
+ "code": "phone",
+ "display_name": "Phone",
+ "field_type": "TEXT",
+ "maxlength": 50,
+ "is_required": false,
+ "is_system_defined": true
+ }, {
+ "id": 12,
+ "code": "start_date",
+ "display_name": "Start Date",
+ "field_type": "DATE",
+ "is_system_defined": true,
+ "maxdate": "2099-12-31",
+ "mindate": "1900-01-01",
+ "is_required": true
+ },
+ { ... }
+ ]
+}
+```
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | Indicates that operation was successful and retrieved a resource-type successfully. |
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | Indicates that no resource-type object was found with provided identifier.
+
+
+## Get All Resource Types
+
+Returns a list of all resource-types sorted by name.
+
+> **`GET /v1/resourcetypes`**
+
+> Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/resourcetypes" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "total_count": 4,
+ "data": [{
+ "id": 1,
+ "name": "Employee",
+ "description": "",
+ "is_human": true,
+ "color": "#000000;1",
+ "fields": [{
+ "id": 52,
+ "code": "udf_department",
+ "display_name": "Department",
+ "field_type": "DDSS",
+ "is_required": false,
+ "is_system_defined": false,
+ "options": [{
+ "id": 27,
+ "name": "Service",
+ "description": null
+ },
+ {
+ "id": 26,
+ "name": "Technical",
+ "description": null
+ },
+ { ... }
+ ]
+ }, {
+ "id": 11,
+ "code": "email",
+ "display_name": "Email",
+ "field_type": "EMAIL",
+ "placeholder_text": "Enter valid email id",
+ "maxlength": 254,
+ "regex": "^[a-zA-Z]+[a-zA-Z0-9._]+@[a-zA-Z]+\\.[a-zA-Z.]{2,5}$",
+ "is_required": false,
+ "is_system_defined": true
+ }, {
+ "id": 46,
+ "code": "udf_employee_no",
+ "display_name": "Employee No.",
+ "field_type": "TEXT",
+ "minlength": 1,
+ "maxlength": 10,
+ "is_required": false,
+ "is_system_defined": false
+ }, {
+ "id": 7,
+ "code": "first_name",
+ "display_name": "First Name",
+ "field_type": "TEXT",
+ "help_text": "",
+ "placeholder_text": "Enter first name",
+ "minlength": 1,
+ "maxlength": 100,
+ "is_required": true,
+ "is_system_defined": true
+ }, {
+ "id": 8,
+ "code": "last_name",
+ "display_name": "Last Name",
+ "field_type": "TEXT",
+ "placeholder_text": "Enter last name",
+ "maxlength": 100,
+ "is_required": false,
+ "is_system_defined": true
+ }, {
+ "id": 14,
+ "code": "last_date",
+ "display_name": "Last Working Date",
+ "field_type": "DATE",
+ "is_required": false,
+ "is_system_defined": true,
+ "maxdate": "2099-12-31",
+ "mindate": "1900-01-01"
+ }, {
+ "id": 26,
+ "code": "phone",
+ "display_name": "Phone",
+ "field_type": "TEXT",
+ "maxlength": 50,
+ "is_required": false,
+ "is_system_defined": true
+ }, {
+ "id": 12,
+ "code": "start_date",
+ "display_name": "Start Date",
+ "field_type": "DATE",
+ "is_system_defined": true,
+ "maxdate": "2099-12-31",
+ "mindate": "1900-01-01",
+ "is_required": true
+ },
+ { ... }
+ ]
+ },
+ { ... }
+ ]
+}
+
+```
+
+
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` | This indicates that the operation was successful and list of resource-types is returned. |
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+
+
+
diff --git a/source/includes/_timesheet.md b/source/includes/_timesheet.md
new file mode 100644
index 00000000000..4b56ecb1e8d
--- /dev/null
+++ b/source/includes/_timesheet.md
@@ -0,0 +1,551 @@
+# Timesheet
+
+## Timesheet Object
+
+>Example Response
+
+```json
+{
+ "id": 34,
+ "resource": {
+ "name": "Andy Murray",
+ "id": 2
+ },
+ "role": {
+ "name": "Business Analyst",
+ "id": 1
+ },
+ "project": {
+ "title": "Mars Rover",
+ "id": 5
+ },
+ "task": {
+ "name": "Planning",
+ "id": 3
+ },
+ "date": "2021-07-26",
+ "time_start": "09:00",
+ "time_end": "14:00",
+ "hours": 5.0,
+ "billing_status": 1,
+ "rate_from": 8,
+ "rate": 99.40,
+ "entry_status": 4,
+ "tags": [
+ "analyst"
+ ],
+ "created_on": "2021-07-27T07:56:17.515125Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2021-07-27T13:23:46.583746Z",
+ "modified_by": {
+ "name": "John Smith",
+ "id": 1146
+ },
+ "submitted_on": "2021-07-27T07:56:17.515125Z",
+ "submitted_by":{
+ "name": "John Doe",
+ "id": 118
+ },
+ "approval_time": "2021-07-27T13:23:46.583746Z",
+ "approver":{
+ "name": "John Smith",
+ "id": 1146
+ },
+}
+```
+
+`Timesheet` entry represents tracking of work done by a resource on a certain project or task for a particular time range. Resource work can be tracked/entered on a project with a defined effort and date along with other custom defined fields.
+
+ATTRIBUTES
+
+Following attributes are available for timesheet entry. Timesheet entry can also be customized to have additional attributes by an Administrator user using eRS Cloud Application. To know about attributes currently applied for timesheet entry please check Timesheet Profile API.
+
+Name | Description
+ ---: | :----
+**id** `integer` | eRS Cloud generated unique identifier for the timesheet entry.
+**resource** `object` | Resource object to which this timesheet entry belongs.
+**project** `object` | Project object for which this timesheet entry was created.
+**task** `object` | Task object defines which task was performed. Tasks could be one of the defined tasks of timesheet's project object.
+**role** `object` | Role object defines which role Resource performed for this timesheet entry.
+**date** `string` | Represents date for which timesheet entry is created.
+**time_start** `string` | Represents starting time of timesheet entry.
+**time_end** `string` | Represents ending time of timesheet entry.
+**hours** `float` | Represents number of hours worked by resource.
+**billing_status** `integer` | Represents billing status for this timesheet entry. Billing Status could be one of `Inherit from Project`, `Billable`, `Non Billable`. This field is available only when financial module is active.
+**rate_from** `integer` | Represents billing rate for this timesheet entry. Billing Rate could be one of `Inherit from Project`, `Inherit from Resource`, `Inherit from Role`, `Custom`. This field is available only when financial module is active.
+**rate** `float` | Represents rate for this timesheet entry. Rate can only be defined when `rate_from` is given as `Custom`. This field is available only when financial module is active.
+**tags** `array of strings` | Tags are the list of strings (labels) attached to this timesheet entry which could be used for the purpose of identification or other information.
+**created_on** `string` | Timestamp at which this timesheet entry was created.
+**created_by** `object` | Object representing user who created this timesheet entry.
+**modified_on** `string` | Represents latest modification timestamp.
+**modified_by** `object` | Object representing most recent user who modified this timesheet entry.
+**submitted_on** `string` | Timestamp at which this timesheet entry was submitted.
+**submitted_by** `object` | Object representing user who submitted this timesheet entry.
+**approval_time** `string` | Timestamp at which this timesheet entry was approved/rejected.
+**approver** `object` | Object representing user who approved/rejected this timesheet entry.
+**entry_status** `integer` | Represents status of timesheet entry. Status could be one of `Draft`, `Submitted`, `Approved` or `Rejected`.
+**comment** `string` | String attached to this timesheet entry which could be used to describe the detail of the work.
+**udf_\*** | Custom user-defined fields are used to capture additional information of timesheet entry. User defined fields can be of multiple types. Custom fields are very useful to configure timesheet entries to best fit requirements. In given example, all keys starting with prefix `udf_` are user defined custom fields. Learn more
+
+## Create a Timesheet Entry
+
+> **`POST v1/timesheet`**
+
+
+> Example Request:
+
+```shell
+ curl -v -X POST "https://app.eresourcescheduler.cloud/rest/v1/timesheet" \
+ -H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+ -H "Content-Type: application/json" \
+ -d '{
+ "resource_id": 1,
+ "project_id" : 9,
+ "date": "2021-07-27",
+ "hours": 5,
+ "udf_location": 349,
+ "comment": "Client presentation is prepared."
+ }'
+```
+
+Creates a new timesheet entry.
+
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**resource_id** `required` | ID of resource object who performed task in this timesheet entry.
+**project_id** `required` | ID of project object on which this timesheet entry is being created.
+**date** `required` | String value representing a date on which task was performed. Date accepts value in ISO 8601 format i.e. yyyy-MM-dd. Date of a timesheet entry cannot be before `start_date` or after `last_date` of the resource for which this timesheet entry is being created.
+**time_start** | Represents start time for timesheet entry. This field accepts value in HH:MM in 24 hour format or HH:MMam or HH:MMpm in 12 hour format.
+**time_end** | Represents end time for timesheet entry. This field accepts value in HH:MM in 24 hour format or HH:MMam or HH:MMpm in 12 hour format. `time_end` must always be ahead of `time_start`.
+**hours** | This defines how many hours the resource worked on a given task. Hours value is a floating point number which could not be 0 or less than 0 and greater than 99999 (When entries for more than 24 hours a day is disabled, maximum value can be up to 24). When user provides `time_start` and `time_end` for a timesheet entry, system automatically calculates hours worked by resource by difference in `time_end` and `time_start`.
_**Note**: The user should either provide `time_start` and `time_end` or `hours`. `time_start` and `time_end` value can also be provided with `hours` when the difference between them is equal to `hours` value._
+**role_id** ⚑⚑ | ID of role object which was performed for this timesheet entry. This could be ID of a role which targeted resource performed.
+**task_id** ⚑ | ID of task object performed in this timesheet entry. This could only be ID of a task which is listed in targeted project.
+**entry_status** `optional` | Integer number (1/2/4/8) representing status of timesheet entry. Timesheet Entry Status value could be one of the following:
**1** for `Draft` : This represents timesheet entry is in Draft state. By default, timesheet entries are created in Draft state.
**2** for `Submitted` : This represents timesheet entry is Submitted.
**4** for `Approved` : This represents timesheet entry is Approved.
**8** for `Rejected` : This represents timesheet entry is Rejected.
+**billing_status** `optional` | Integer number (1/2/4) representing billing status of the timesheet entry. Billing status value could be one of the following :
**1** for `Inherit from Project` : This represents billing status will be the same as given for the project associated with this timesheet entry.
**2** for `Billable` : This defines billing status as billable for this timesheet entry.
**4** for `Non Billable` : This is used to set the timesheet entry to non billable.
_**Note**: Default value of billing status can be set from Administrator Timesheet Settings. This field is available only when financial module is active._ |
+**rate_from** `optional` | Integer number (1/2/4/8) representing billing rate of the timesheet entry. Billing rate value could be one of the following :
**1** for `Inherit from Project` : This represents billing rate will be the same as given for the project associated with this timesheet entry.
**2** for `Inherit from Resource` : This represents billing rate will be the same as given for the resource associated with this timesheet entry.
**4** for `Inherit from Role` : This represents billing rate will be the same as given for the performing role associated with this timesheet entry.
**8** for `Custom` : Custom hourly rate can be defined on a timesheet entry with this billing rate value.
_**Note**: Default value of billing rate can be set from Administrator Timesheet Settings. This field is available only when financial module is active._ |
+**rate** `optional` | This defines hourly billing rate associated with this timesheet entry. Rate value is a floating point number which can not be less than 0 and greater than 99999999.99. Rate can only be defined when value of `rate_from` is 8, i.e `Custom`.
_**Note**: This field is available only when financial module is active._
+**tags** ⚑ | An optional array of strings which could be attached to this timesheet entry object as labels. This can be useful for the purpose of identification or other information.
+**comment** `optional` | An optional string which could be attached to this timesheet entry. This can be useful for describing the detail of the work.
+**udf_\*** ⚑⚑ | A user with admin rights can add custom fields. These fields can be used to capture additional information in timesheet entry. The value for user defined fields can be passed as shown in example. In given example `udf_location`
_**Note**: User with Administrator rights can make fields marked with ⚑ mandatory and remove fields marked with ⚑, from timesheet profile using eRS Cloud Application. If mandatory fields are not passed with a valid value or removed fields are passed while creating timesheet entry, the operation will fail with response code **400**_.
+
+### Returns
+
+| Code |Description |
+ :--- | :---- |
+| **201** `Created` | This status code indicates that the operation was successful and a timesheet entry is created successfully.|
+**400** `Bad Request` | Bad Request occurs when a request is malformed, syntactically incorrect, missing required parameters or any unknown parameter is passed. Additionally, Bad Request may also occur in one of these conditions:
Timesheet entry `date` is given before the `start_date` of resource or after the `last_date` of resource (if resource has a `last_date` defined).
Trying to create timesheet entry on archived resource.
Trying to create timesheet entry on archived project.
Parameters passed in timesheet entry are violating one or more pre-defined configurations of resource or project from Timesheet Setup using eRS Cloud Application.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+
+## List Timesheets
+
+Returns list of timesheet entries.
+
+> **`GET /v1/timesheet`**
+
+> Example Request
+
+```shell
+curl -v "https://app.eresourcescheduler.cloud/rest/v1/timesheet?\
+start=2021-07-01&end=2021-07-31" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+>Example Request With Offset And Limit
+
+```shell
+curl -v "https://app.eresourcescheduler.cloud/rest/v1/timesheet?\
+start=2021-07-01&end=2021-07-31&offset=1&limit=10" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "total_count": 7,
+ "data": [{
+ "id": 34,
+ "resource": {
+ "name": "Andy Murray",
+ "id": 2
+ },
+ "role": {
+ "name": "Business Analyst",
+ "id": 1
+ },
+ "project": {
+ "title": "Mars Rover",
+ "id": 5
+ },
+ "task": {
+ "name": "Planning",
+ "id": 3
+ },
+ "date": "2021-07-26",
+ "time_start": "09:00",
+ "time_end": "14:00",
+ "hours": 5.0,
+ "billing_status": 1,
+ "rate_from": 8,
+ "rate": 99.40,
+ "entry_status": 4,
+ "tags": [
+ "analyst"
+ ],
+ "created_on": "2021-07-27T07:56:17.515125Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2021-07-27T13:23:46.583746Z",
+ "modified_by": {
+ "name": "John Smith",
+ "id": 943
+ },
+ "submitted_on": "2021-07-27T07:56:17.515125Z",
+ "submitted_by":{
+ "name": "John Doe",
+ "id": 118
+ },
+ "approval_time": "2021-07-27T13:23:46.583746Z",
+ "approver":{
+ "name": "John Smith",
+ "id": 1146
+ },
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`500`**. _Maximum value of `limit` can be_ **`5000`**.
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**.
+**start** `optional` | String value representing start date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter timesheet entries on or after this date.
+**end** `optional` | String value representing end date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter timesheet entries on or before this date.
+||_**Note**: By default if `start` & `end` arguments are omitted, then timesheet entries of current month will be returned. If timesheet entries of a certain period are needed, then both `start` & `end` arguments are required. If only one argument `start` or `end` is passed then a bad request error is raised._
+
+
+### Returns
+
+
+| Code | Description |
+| ---: | :---- |
+| **200** `OK` |This indicates that the operation was successful and list of timesheet entries is returned. |
+**400** `Bad Request` | Bad Request may occur when offset or limit value is negative integer.|
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+
+
+## Retrieve a Timesheet Entry
+
+> **`GET v1/timesheet/{ID}`**
+
+> Example Request
+
+```shell
+curl -v -X GET "https://app.eresourcescheduler.cloud/rest/v1/timesheet/25" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+> Example Response
+
+```json
+{
+ "id": 25,
+ "resource": {
+ "name": "Andy Murray",
+ "id": 2
+ },
+ "role": {
+ "name": "Business Analyst",
+ "id": 1
+ },
+ "project": {
+ "title": "Mars Rover",
+ "id": 5
+ },
+ "task": {
+ "name": "Planning",
+ "id": 3
+ },
+ "date": "2021-07-26",
+ "time_start": "09:00",
+ "time_end": "14:00",
+ "hours": 5.0,
+ "billing_status": 1,
+ "rate_from": 8,
+ "rate": 99.40,
+ "entry_status": 4,
+ "tags": [
+ "analyst"
+ ],
+ "created_on": "2021-07-27T07:56:17.515125Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2021-07-27T13:23:46.583746Z",
+ "modified_by": {
+ "name": "John Smith",
+ "id": 1146
+ },
+ "submitted_on": "2021-07-27T07:56:17.515125Z",
+ "submitted_by":{
+ "name": "John Doe",
+ "id": 118
+ },
+ "approval_time": "2021-07-27T13:23:46.583746Z",
+ "approver":{
+ "name": "John Smith",
+ "id": 1146
+ },
+}
+```
+Retrieves the details of an existing timesheet entry. You only need to provide the unique timesheet identifier that was returned upon timesheet creation.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This status code indicates that the operation was successful and a timesheet entry returned successfully.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested timesheet entry does not exist (i.e. There is no timesheet entry with given ID). This may also occur when requesting a timesheet entry that has been deleted.
+
+## Search Timesheet Entries
+
+
+
+> **`POST /v1/timesheet/search`**
+
+> Example Request For Filter In JSON Format
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/timesheet/search?\
+start=2021-07-01&end=2021-07-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "id": 1
+ }'
+```
+
+> Example Request For Filter By Passing multiple filters In JSON Format
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/timesheet/search?\
+start=2021-07-01&end=2021-07-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "resource":{"id":2},
+ "project":{"id":9},
+ "role_id:eq": 1,
+ "tags:any": ["analyst","admin"]
+ }'
+```
+
+> Example Response
+
+```json
+{
+ "total_count": 7,
+ "data": [{
+ "id": 34,
+ "resource": {
+ "name": "Andy Murray",
+ "id": 2
+ },
+ "role": {
+ "name": "Business Analyst",
+ "id": 1
+ },
+ "project": {
+ "title": "Mars Rover",
+ "id": 5
+ },
+ "task": {
+ "name": "Planning",
+ "id": 3
+ },
+ "date": "2021-07-26",
+ "time_start": "09:00",
+ "time_end": "14:00",
+ "hours": 5.0,
+ "billing_status": 1,
+ "rate_from": 8,
+ "rate": 99.40,
+ "entry_status": 4,
+ "tags": [
+ "analyst"
+ ],
+ "created_on": "2021-07-27T07:56:17.515125Z",
+ "created_by": {
+ "name": "John Doe",
+ "id": 118
+ },
+ "modified_on": "2021-07-27T13:23:46.583746Z",
+ "modified_by": {
+ "name": "John Smith",
+ "id": 1146
+ },
+ "submitted_on": "2021-07-27T07:56:17.515125Z",
+ "submitted_by":{
+ "name": "John Doe",
+ "id": 118
+ },
+ "approval_time": "2021-07-27T13:23:46.583746Z",
+ "approver":{
+ "name": "John Smith",
+ "id": 1146
+ },
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields less records) _Default value of `limit` is_ **`500`**. _Maximum value of `limit` can be_ **`5000`**.
+**offset** `optional` | Offset keyword is used to skip n items. If offset value is given as 10, then first 10 records will be skipped from result set. Offset is often used together with the Limit keyword. _Default value of `offset` is_ **`0`**.
+**start** `optional` | String value representing start date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter timesheet entries on or after this date.
+**end** `optional` | String value representing end date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to filter timesheet entries on or before this date.
+||_**Note**: By default if `start` & `end` arguments are omitted, then timesheet entries of current month will be returned. If timesheet entries of a certain period are needed, then both `start` & `end` arguments are required. If only one argument `start` or `end` is passed then a bad request error is raised._
+
+Search Timesheet API allows filtering the results set in various ways. This enables a great power to find out what is needed. eRS Cloud API also allows filtering on custom defined fields with multiple operators and conditions to cover up complex scenarios for searching.
+
+A filter condition consists of three components which are **_field_**, **_operator_** and **_value_**. For example, fetching only those timesheets having tag `analyst` or `admin`, could be achieved by adding `"tags:any": ["analyst", "admin"]` to request body. If operator is not supplied, it takes default operator for field.
+
+Below is a list of available fields, which allow filtering of timesheet entries:
+
+|**Field Type** | **Operator** | **Example**|
+:--| :--- | :--- | :--- |
+**role_id**|
| `"entry_status:eq": 1` `"entry_status:neq": 2` `"entry_status:any": [4, 8]` `"entry_status:none": [1, 2]`
+_Additionally, timesheet entries can also be filtered using resource fields, project fields and custom fields of timesheet. An example request for fetching only timesheet entry having `resource_id` as 2, `project_id` as 9 and `role_id` as 1 is shown._
+
+## Update a Timesheet Entry
+
+Updates the specified timesheet entry by setting values of parameters passed. Values of any parameters which are not provided will be unchanged. To unset existing value for a parameter, just pass an empty value i.e. `null`.
+
+> **`PUT /v1/timesheet/{ID}`**
+
+> Example Request
+
+```shell
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest/v1/timesheet/25" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "resource_id": 3,
+ "project_id" : 4,
+ "hours" : 5,
+ "date": "2021-07-24",
+ "comment": "Client presentation is prepared."
+ }'
+```
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :----
+**resource_id** `required` | ID of resource object which is being used in timesheet entry. This will throw an error if you post an empty value.
+**project_id** `required` | ID of project object which this timesheet entry is being created for. This will throw an error if you post an empty value.
+**date** `required` | String value representing a date on which task was performed. Date accepts value in ISO 8601 format i.e. yyyy-MM-dd. Date of a timesheet entry cannot be before `start_date` or after `last_date` of the resource for which this timesheet entry is being created.
+**time_start** | Represents start time for timesheet entry. This field accepts value in HH:MM in 24 hour format or HH:MMam or HH:MMpm in 12 hour format.
+**time_end** | Represents end time for timesheet entry. This field accepts value in HH:MM in 24 hour format or HH:MMam or HH:MMpm in 12 hour format. `time_end` must always be ahead of `time_start`.
+**hours** | This defines how many hours the resource worked on a given task. Hours value is a floating point number which could not be 0 or less than 0 and greater than 99999 (When entries for more than 24 hours a day is disabled, maximum value can be up to 24).
_**Note**: The user should either provide `time_start` and `time_end` or `hours`. `time_start` and `time_end` value can also be provided with `hours` when the difference between them is equal to `hours` value._
+**role_id** ⚑⚑ | ID of role object which was performed for this timesheet entry. This could be ID of a role which targeted resource performed.
+**task_id** ⚑ | ID of task object performed in this timesheet entry. This could only be ID of a task which is listed in targeted project.
+**entry_status** `optional` | Integer number (1/2/4/8) representing status of timesheet entry. Timesheet Entry Status value could be one of the following:
**1** for `Draft` : This represents timesheet entry is in Draft state. By default, timesheet entries are created in Draft state.
**2** for `Submitted` : This represents timesheet entry is Submitted.
**4** for `Approved` : This represents timesheet entry is Approved.
**8** for `Rejected` : This represents timesheet entry is Rejected.
+**billing_status** `optional` | Integer number (1/2/4) representing billing status of the timesheet entry. Billing status value could be one of the following :
**1** for `Inherit from Project` : This represents billing status will be the same as given for the project associated with this timesheet entry.
**2** for `Billable` : This defines billing status as billable for this timesheet entry.
**4** for `Non Billable` : This is used to set the timesheet entry to non billable.
_**Note**: Default value of billing status can be set from Administrator Timesheet Settings. This field is available only when financial module is active._ |
+**rate_from** `optional` | Integer number (1/2/4/8) representing billing rate of the timesheet entry. Billing rate value could be one of the following :
**1** for `Inherit from Project` : This represents billing rate will be the same as given for the project associated with this timesheet entry.
**2** for `Inherit from Resource` : This represents billing rate will be the same as given for the resource associated with this timesheet entry.
**4** for `Inherit from Role` : This represents billing rate will be the same as given for the performing role associated with this timesheet entry.
**8** for `Custom` : Custom hourly rate can be defined on a timesheet entry with this billing rate value.
_**Note**: Default value of billing rate can be set from Administrator Timesheet Settings. This field is available only when financial module is active._ |
+**rate** `optional` | This defines hourly billing rate associated with this timesheet entry. Rate value is a floating point number which can not be less than 0 and greater than 99999999.99. Rate can only be defined when value of `rate_from` is 8, i.e `Custom`.
_**Note**: This field is available only when financial module is active._
+**tags** ⚑ | An optional array of strings which could be attached to this timesheet entry object as labels. This can be useful for the purpose of identification or other information.
+**comment** `optional` | An optional string which could be attached to this timesheet entry. This can be useful for describing the detail of the work.
_**Note**: Existing comments cannot be updated but new comments can always be added with timesheet updates._
+**udf_\*** ⚑⚑ | A user with Administrator rights can add custom fields. These fields can be used to capture additional information in timesheet entry. Learn more
_**Note**: User with Administrator rights can make fields marked with ⚑ mandatory and remove fields marked with ⚑, from timesheet profile using eRS Cloud Application. If mandatory fields are not passed with a valid value or removed fields are passed while creating timesheet entry, the operation will fail with response code **400**_.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This indicates that the operation was successful and a timesheet entry updated successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, empty required parameters or any unknown parameter is passed. Additionally, Bad request may also occur in one of these conditions :
Trying to update `time_start` or `time_end` such that `time_end` gets earlier than `time_start`.
Trying to update `date` of timesheet entry before the `start_date` of resource or after `last_date` of resource. (if resource has a `last_date` defined).
Trying to update timesheet entry of archived resource.
Trying to update timesheet entry of archived project.
Parameters passed in timesheet entry are violating one or more pre-defined configurations of resource or project from Timesheet Setup using eRS Cloud Application.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested timesheet entry does not exist (i.e. There is no timesheet entry with given ID). This may also occur when requesting a timesheet entry that has been deleted.
+
+## Update a Timesheet Entry Status
+
+Updates status of a specified timesheet entry by setting different integer values set for status.
+
+> **`PUT /v1/timesheet/status/{ID}`**
+
+> Example Request
+
+```shell
+curl -v -X PUT "https://app.eresourcescheduler.cloud/rest/v1/timesheet/status/25" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-H "Content-Type: application/json" \
+-d '{
+ "entry_status": 2
+ }'
+```
+
+REQUEST BODY PARAMETERS
+
+Name | Description
+ ---: | :---- |
+**entry_status** `optional` | Integer number (1/2/4/8) representing status of timesheet entry. Timesheet Entry Status value could be one of the following:
**1** for `Draft` : This represents timesheet entry is in Draft state. By default, timesheet entries are created in Draft state.
**2** for `Submitted` : This represents timesheet entry is Submitted.
**4** for `Approved` : This represents timesheet entry is Approved.
**8** for `Rejected` : This represents timesheet entry is Rejected.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This indicates that the operation was successful and status of timesheet entry has been updated successfully.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect, empty required parameters or any unknown parameter is passed. Additionally, Bad request may also occur in one of these conditions :
Trying to update timesheet entry status other then `Draft`, `Submitted`, `Approved` or `Rejected`(passing values other than 1/2/4/8 for `entry_status`).
Trying to update timesheet entry status targeted on an archived resource
Trying to update timesheet entry status targeted on an archived project.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
+**404** `Not Found` | Not Found error occurs when requested timesheet entry does not exist (i.e. There is no timesheet entry with given ID). This may also occur when requesting a timesheet entry that has been deleted.
+
+## Delete a Timesheet Entry
+
+Permanently deletes a timesheet entry. It cannot be undone.
+
+> **`DELETE /v1/timesheet/{ID}`**
+
+
+> Example Request
+
+```shell
+curl -v -X DELETE "https://app.eresourcescheduler.cloud/rest\
+/v1/timesheet/1" -H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+
+### Returns
+
+
+| Code | Description
+| ---: | :----
+| **200** `OK` |This status code indicates that the operation was successful and a timesheet entry deleted successfully. |
+| **403** `Forbidden` | Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.|
+| **404** `Not Found` | Not Found error occurs when requested timesheet entry does not exist or is already deleted.
diff --git a/source/includes/_timesheetprofile.md b/source/includes/_timesheetprofile.md
new file mode 100644
index 00000000000..688759167ae
--- /dev/null
+++ b/source/includes/_timesheetprofile.md
@@ -0,0 +1,147 @@
+
+# Timesheet Profile
+
+## Timesheet Profile Object
+
+Timesheet profile object represents timesheet profile.
+
+> **`/v1/timesheet/fields`**
+
+> Example Request
+
+```shell
+curl -v \
+"https://app.eresourcescheduler.cloud/rest/v1/timesheet/fields" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV"
+```
+> Example Response
+
+```json
+{
+ "id": 43,
+ "code": "rate_from",
+ "display_name": "Billing Rate",
+ "field_type": "RTFRM",
+ "minnum": 0,
+ "is_system_defined": true,
+ "is_required": false
+},
+{
+ "id": 42,
+ "code": "billing_status",
+ "display_name": "Billing Status",
+ "field_type": "BLSTS",
+ "minnum": 0,
+ "is_system_defined": true,
+ "is_required": false
+},
+{
+ "id": 62,
+ "code": "date",
+ "display_name": "Date",
+ "field_type": "DATE",
+ "is_system_defined": true,
+ "is_required": true
+},
+{
+ "id": 63,
+ "code": "hours",
+ "display_name": "Effort",
+ "field_type": "TSEFFORT",
+ "maxnum": 99999,
+ "is_system_defined": true,
+ "is_required": true
+}
+{
+ "id": 65,
+ "code": "time_end",
+ "display_name": "End Time",
+ "field_type": "TIMEWZ",
+ "is_system_defined": true,
+ "is_required": false
+},
+{
+ "id": 31,
+ "code": "role_id",
+ "display_name": "Performing Role",
+ "field_type": "ROLEPS",
+ "is_required": false,
+ "is_system_defined": true
+ "options": [
+ {
+ "id": 5,
+ "name": "Architect",
+ "description": null
+ },
+ {...},
+ {...}
+ ]
+},
+{
+ "id": 3,
+ "code": "project_id",
+ "display_name": "Project",
+ "field_type": "PRJSS",
+ "is_required": true,
+ "is_system_defined": true
+},
+{
+ "id": 2,
+ "code": "resource_id",
+ "display_name": "Resource",
+ "field_type": "RSRSS",
+ "is_required": true,
+ "is_system_defined": true
+},
+{
+ "id": 64,
+ "code": "time_start",
+ "display_name": "Start Time",
+ "field_type": "TIMEWZ",
+ "is_system_defined": true,
+ "is_required": false
+},
+{
+ "id": 32,
+ "code": "tags",
+ "display_name": "Tags",
+ "field_type": "TAGS",
+ "is_required": false,
+ "is_system_defined": true
+},
+{
+ "id": 30,
+ "code": "task_id",
+ "display_name": "Task",
+ "field_type": "TSKSS",
+ "is_required": false,
+ "is_system_defined": true
+}
+
+```
+
+
+
+ATTRIBUTES
+
+Name | Description
+| ---: | :---- |
+**id** `integer` | Represents unique identification number of this field, which can be used to refer or search it.
+**code** `string` | It represents the unique code of the field which is referred as API code. This code acts as `key` in API response and the same must be used as `key` to pass values for a POST or PUT request.
+**field_type** `string` | Represents the type of field. For example TEXT (for Text Field), INT (for Integer Number field), DDSS (for Dropdown Single Select Field), etc. See User Defined Fields to know more about different field types.
+**display_name** `string` |Name of this field to identify it.
+**is_system_defined** `boolean` | Indicates whether this field is system defined or a custom field. Fields which are system defined can not be customized.
+**is_required** `boolean` |Indicates whether this field is mandatory or not. If this field is a required field then a valid value for this field must be passed while creating such object and while updating object (if this field is intended to update).
+**regex** `string` | Represents regular expression which must be matched by value for this field. Only applicable for text fields.
+**fields.minlength** `integer` | Represents minimum no of characters in value this field can accept. Only applicable for text fields.
+**fields.maxlength** `integer` | Represents maximum no of characters in value this field can accept. Only applicable for text fields.
+**minnum** `integer` | Represents minimum value this field can accept. Only applicable for numeric fields.
+**maxnum** `integer` | Represents maximum value this field can accept. Only applicable for numeric fields.
+**mindate** `string` |Represents minimum value this field can accept. Only applicable for date / date time fields.
+**maxdate** `string` |Represents maximum value this field can accept. Only applicable for date / date time fields.
+**options** `array of objects` | Field types such as Dropdown Single Select, Dropdown Multi Select, Radio Group etc. ( See User Defined Fields to know more. ) Allows user to pick one or more from these available options.
+**options.id** `integer` | Represents unique identification number for the individual option object.
+**options.name** `string` | Represents name or content of option object.
+**options.color** `string` | Allows a user to store color code of option object. Only applicable for LABEL type fields.
+
+
diff --git a/source/includes/_udftypes.md b/source/includes/_udftypes.md
new file mode 100644
index 00000000000..513fbce4da6
--- /dev/null
+++ b/source/includes/_udftypes.md
@@ -0,0 +1,51 @@
+
+# User Defined Fields
+
+
+>Example Response:
+
+```json
+{
+ ...
+ "emp_birthday": "1997-01-27",
+ "qualification": "MBA"
+ ...
+}
+```
+
+As the name shows, these fields are user-defined custom fields. A user with Administrator rights can add such custom fields using eRS Cloud Application. These fields can be used to capture additional information in Resource, Project, Requirement, Booking and Timesheet forms.
+
+User defined fields are filterable. Also, user can configure the visibility of such fields in the different forms, for example a field named `employee_id` can be created which is meant only for `Employee` type of resources.
+
+There are seventeen types of different fields available for different use cases. Each type of field has it's own set of attributes which can be configured to fit your requirements. Once such fields are added and applied, the response for that object will contain these along with normal attributes.
+
+
+_**Note**: There can be a maximum of 125 user-defined fields._
+
+
+
+## Types of User Defined Fields
+
+
+User can create one of the following types of field.
+
+
+Name |Description
+:- | :-
+**Simple Text** `string` | Allows user to enter any combination of letters and numbers. Also, it can be configured to have different validations like `minlength`, `maxlength` and `regex` to fit most requirements.
+**Multi Line Rich Text** `string` | Allows user to enter long rich text (up to 2000 characters). This type of field allows formatting such as adding headers, paragraphs, hyperlinks, **bold** and _italic_ text etc.
+**Integer Number** `integer` | Allows user to enter numeric data. This is useful for fields like `emp_id`, `ref_no` etc. These fields can be configured to have validations like `minnum` and `maxnum`.
+**Fractional Number** `number` | Allows user to enter floating point number. This is useful for fields like `geo_coordinates`, `mean_distance` etc. This type of field can also have validations like `minnum` and `maxnum`.
+**Date** `string` | Allows user to enter date value from a popup calendar. This field takes input in ISO 8601 extended notation for date value i.e. yyyy-MM-dd. Example use case of this type of fields could be like `emp_birth_dae`, `date_of_delivery`, `date_of_completion` etc. Available validations for these fields are `mindate` and `maxdate`.
+**DateTime** `string` | This type of field can be used where a specific instance of time needs to be recorded. This field takes input in ISO 8601 extended notation for date and time value i.e. yyyy-MM-ddTHH:mm:ssZ. This field supports time zone offset as well. Example use case of this type of fields could be like `eta`, `generated_at` etc.
+**URL** `string` | Allows user to enter a valid link address. This field takes string input which should be a valid URL. This type of field could be used to store a hyperlink to a website or a network resource.
+**Email** `string` | Allows user to enter an email address, which is validated to ensure the proper format.
+**Checkbox** `boolean` | Allows user to select or deselect a value using checkbox. This field takes a boolean value as input. Example use case could be like `is_enabled`, `is_active` etc.
+**Radio Group** `integer` | Allows user to select a single value from available values. This field can be configured to have multiple options from which the user can select one.
+**Drop Down Single Select** `integer` | Allows user to select a single value from the dropdown list of available options. This field can be configured to have a pick list of multiple options from which the user can select one.
+**Checkbox Group** `integer array` | Allows user to select one or more values from a group of check boxes. This is useful where user needs to pick multiple values from available options. This field can be configured to have a pick list of multiple options from which the user can select multiple.
+**Dropdown Multi select** `integer array` | Allows user to select multiple values from the dropdown list. This field can be configured to have a pick list of multiple options from which user can select one or more options. Though it is similar to checkbox group field, it additionally allows to search from available options and is recommended when there is a large number of options.
+**Color Picker** `string`| Allows user to store a color code for an object. This is useful to visually identify an object when presenting in user interface. This field takes input in string format of hexadecimal color code with foreground color separated by semicolon `;` i.e #XXXXXX;1/0. Here X represent hexadecimal digit for background color, 1 represents white foreground color and 0 represents black foreground color. For example if `red` background with `white` foreground (text color) needs to be stored, then value should be `#FF0000;1`.
+**Label** `integer` | Allows user to select a single value with color, from the dropdown list. This field can be configured to have a pick list of multiple options from which the user can select one. These fields are useful for visual representation with meaningful labels. For example a field named `status` can be created having options such as Active , On Hold, Delayed .
+**User Single Select** `integer` | Allows user to select a single value from the dropdown list of available users.
+**User Multi Select** `integer array` | Allows user to select multiple user values from the dropdown list of available users.
\ No newline at end of file
diff --git a/source/includes/_utilization.md b/source/includes/_utilization.md
new file mode 100644
index 00000000000..a81011a78e0
--- /dev/null
+++ b/source/includes/_utilization.md
@@ -0,0 +1,436 @@
+
+# Utilization
+
+
+This API endpoint is used to query the calculated utilization of resources and projects. The API also allows fetching out planned and actual utilization with different filter criteria in various ways. This enables a great power to find out what is needed. eRS Cloud API also allows filtering on custom-defined fields with multiple operators and conditions to cover complex scenarios.
+
+
+## Get Utilization
+
+> **`POST /v1/utilization`**
+
+> Example: Get utilization by resources
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/utilization?\
+view=resource&start=2022-05-01&end=2022-05-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+```
+
+> Response
+
+```json
+{
+ "end_date": "2022-05-31",
+ "offset": 0,
+ "total_count": 11,
+ "limit": 10,
+ "start_date": "2022-05-01",
+ "resources": [
+ {
+ "id": 1,
+ "name": "Albert Murphy",
+ "total_planned_hrs": 160.79
+ },
+ {
+ "id": 8,
+ "name": "Ayn Dante",
+ "total_planned_hrs": 71.22
+ },
+ {
+ "id": 2,
+ "name": "Chris Rose",
+ "total_planned_hrs": 138.6
+ },
+ {
+ "id": 10,
+ "name": "Emily Eliot",
+ "total_planned_hrs": 187.2
+ },
+ {
+ "id": 9,
+ "name": "Jayden Brock",
+ "total_planned_hrs": 164.39
+ },
+ {
+ "id": 4,
+ "name": "Joanna Collins",
+ "total_planned_hrs": 114.0
+ },
+ {
+ "id": 3,
+ "name": "Martha Day",
+ "total_planned_hrs": 66.0
+ },
+
+ { ... },
+ { ... }
+ ]
+}
+```
+
+> Example: Get utilization by projects
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/utilization?\
+view=project&start=2022-05-01&end=2022-05-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+```
+
+> Response
+
+```json
+{
+ "end_date": "2022-05-31",
+ "offset": 0,
+ "total_count": 6,
+ "limit": 10,
+ "start_date": "2022-05-01",
+ "projects": [
+ {
+ "id": 1,
+ "title": "Apollo 11",
+ "total_planned_hrs": 274.0
+ },
+ {
+ "id": 5,
+ "title": "Falcon 9",
+ "total_planned_hrs": 132.0
+ },
+ {
+ "id": 2,
+ "title": "Hubble Telescope",
+ "total_planned_hrs": 422.59
+ },
+ {
+ "id": 3,
+ "title": "Mangalyaan",
+ "total_planned_hrs": 229.20
+ },
+ {
+ "id": 6,
+ "title": "Mars Express",
+ "total_planned_hrs": 213.79
+ },
+ {
+ "id": 4,
+ "title": "Mars Rover",
+ "total_planned_hrs": 208.79
+ }
+
+ ]
+}
+```
+
+> Example: Get utilization by projects using project filter
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/utilization?\
+view=project&start=2022-05-01&end=2022-05-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+-d '{
+ "project":{
+ "project_start_date:gt":"2022-01-01",
+ "tags":["Medium","High"]
+ }
+ }'
+```
+
+> Response
+
+```json
+{
+ "end_date": "2022-05-31",
+ "offset": 0,
+ "total_count": 2,
+ "limit": 10,
+ "start_date": "2022-05-01",
+ "projects": [
+ {
+ "id": 1,
+ "title": "Apollo 11",
+ "total_planned_hrs": 274.0
+ },
+ {
+ "id": 2,
+ "title": "Hubble Telescope",
+ "total_planned_hrs": 422.59
+ }
+ ]
+}
+```
+
+> Example: Get planned and actual utilization
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/utilization?\
+start=2022-05-01&end=2022-05-31&data=actual,planned" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+```
+
+> Response
+
+```json
+{
+ "end_date": "2022-05-31",
+ "offset": 0,
+ "total_count": 11,
+ "limit": 10,
+ "start_date": "2022-05-01",
+ "resource": [
+ {
+ "id": 1,
+ "name": "Albert Murphy",
+ "total_actual_hrs": 10.4,
+ "total_planned_hrs": 160.79,
+ },
+ {
+ "id": 8,
+ "name": "Ayn Dante",
+ "total_actual_hrs": 0.0,
+ "total_planned_hrs": 71.22
+ },
+ {
+ "id": 2,
+ "name": "Chris Rose",
+ "total_actual_hrs": 30.50,
+ "total_planned_hrs": 138.6
+ },
+ {
+ "id": 10,
+ "name": "Emily Eliot",
+ "total_actual_hrs": 12.8,
+ "total_planned_hrs": 187.2
+ },
+ {
+ "id": 9,
+ "name": "Jayden Brock",
+ "total_actual_hrs": 0.0,
+ "total_planned_hrs": 164.39
+ },
+ {
+ "id": 4,
+ "name": "Joanna Collins",
+ "total_actual_hrs": 15.0,
+ "total_planned_hrs": 114.0
+ },
+ {
+ "id": 3,
+ "name": "Martha Day",
+ "total_actual_hrs": 25.40,
+ "total_planned_hrs": 66.0
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+> Example: Get planned and actual utilization with daily breakup
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/utilization?\
+start=2022-05-01&end=2022-05-05&data=actual,planned&daily_hrs=true" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+```
+
+> Response
+
+```json
+{
+ "end_date": "2022-05-05",
+ "offset": 0,
+ "total_count": 11,
+ "limit": 10,
+ "start_date": "2022-05-01",
+ "resource": [
+ {
+ "daily_actual_hrs": {
+ "2022-05-01": 3.0,
+ "2022-05-02": 2.0,
+ "2022-05-03": 5.0,
+ "2022-05-04": 0.0,
+ "2022-05-05": 3.0,
+ },
+ "daily_planned_hrs": {
+ "2022-05-01": 5.0,
+ "2022-05-02": 5.0,
+ "2022-05-03": 5.0,
+ "2022-05-04": 3.0,
+ "2022-05-05": 0.0,
+ },
+
+ "id": 1,
+ "name": "Albert Murphy",
+ "total_actual_hrs": 13.0,
+ "total_planned_hrs": 18.0,
+ },
+ {
+ "daily_actual_hrs": {
+ "2022-05-01": 4.0,
+ "2022-05-02": 4.0,
+ "2022-05-03": 4.0,
+ "2022-05-04": 4.0,
+ "2022-05-05": 5.0,
+ },
+ "daily_planned_hrs": {
+ "2022-05-01": 8.0,
+ "2022-05-02": 8.0,
+ "2022-05-03": 8.0,
+ "2022-05-04": 8.0,
+ "2022-05-05": 8.0,
+ },
+
+ "id": 8,
+ "name": "Ayn Dante",
+ "total_actual_hrs": 21.0,
+ "total_planned_hrs": 40.0,
+ },
+ {...},
+ {...}
+ ]
+}
+```
+
+> Example: Get capacity hours by resource
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/utilization?\
+view=resource&data=capacity&start=2022-05-01&end=2022-05-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+```
+
+> Response
+
+```json
+{
+ "end_date": "2022-05-31",
+ "offset": 0,
+ "total_count": 11,
+ "limit": 10,
+ "start_date": "2022-05-01",
+ "resources": [
+ {
+ "id": 1,
+ "name": "Albert Murphy",
+ "total_capacity_hrs": 176.0
+ },
+ {
+ "id": 8,
+ "name": "Ayn Dante",
+ "total_capacity_hrs": 528.0
+ },
+ {
+ "id": 2,
+ "name": "Chris Rose",
+ "total_capacity_hrs": 220.0
+ },
+ {
+ "id": 10,
+ "name": "Emily Eliot",
+ "total_capacity_hrs": 181.5
+ },
+ {
+ "id": 9,
+ "name": "Jayden Brock",
+ "total_capacity_hrs": 0.0
+ },
+ {
+ "id": 4,
+ "name": "Joanna Collins",
+ "total_capacity_hrs": 176.0
+ },
+ {
+ "id": 3,
+ "name": "Martha Day",
+ "total_capacity_hrs": 528.0
+ },
+ { ... },
+ { ... }
+ ]
+}
+```
+
+> Example: Get requested hours by project
+
+```shell
+curl -X POST "https://app.eresourcescheduler.cloud/rest/v1/utilization?\
+view=project&data=requested&start=2022-05-01&end=2022-05-31" \
+-H "Content-Type: application/json" \
+-H "Authorization: Bearer B8x5Vj1O65r6wnoV" \
+```
+
+> Response
+
+```json
+{
+ "end_date": "2022-05-31",
+ "offset": 0,
+ "total_count": 6,
+ "limit": 10,
+ "start_date": "2022-05-01",
+ "projects": [
+ {
+ "id": 1,
+ "title": "Apollo 11",
+ "total_requested_hrs": 274.0
+ },
+ {
+ "id": 5,
+ "title": "Falcon 9",
+ "total_planned_hrs": 132.0
+ },
+ {
+ "id": 2,
+ "title": "Hubble Telescope",
+ "total_planned_hrs": 422.59
+ },
+ {
+ "id": 3,
+ "title": "Mangalyaan",
+ "total_planned_hrs": 229.20
+ },
+ {
+ "id": 6,
+ "title": "Mars Express",
+ "total_planned_hrs": 213.79
+ },
+ {
+ "id": 4,
+ "title": "Mars Rover",
+ "total_planned_hrs": 208.79
+ }
+
+ ]
+}
+```
+
+REQUEST QUERY PARAMETERS
+
+|Name|Description|
+|-:|:-|
+**start** `optional` | String value representing start date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to get utilization on or after this date.
+**end** `optional` | String value representing end date in ISO 8601 extended notation for date i.e. yyyy-MM-dd. This is used to get utilization on or before this date.
+||_**Note**: By default, if `start` & `end` arguments are omitted, then utilization of the current month will be returned. If utilization of a specific period is required, then both `start` & `end` arguments must be passed._
+**limit** `optional` | The limit keyword is used to limit the number of records returned from a result set. If a limit count is given, no more than that many records will be returned (but possibly less, if the query itself yields fewer records) _Default value of `limit` is_ **`10`**. _Maximum value of `limit` can be_ **`25`**.
+**offset** `optional` | Offset keyword is used to skip n items. If the offset value is given as 10, then the first 10 records will be skipped from the result set. Offset is often used together with the limit keyword. _Default value of `offset` is_ **`0`**.
+**view** `optional` | This parameter allows you to select from the two available views i.e. **resource** or **project**. The `Resource` view aggregates utilization data on resources, whereas the `project` view aggregates data on projects. _Default value of `view` is_ **`resource`**.
+**data** `optional` | This parameter allows querying various metrics such as planned utilization, actual utilization, resource capacity, and requested hours. The keys for different metrics are listed below: `planned`: for planned utilization `actual`: for actual utilization `capacity`: for resource capacity (only applicable when the view is set to resource) `requested`: for requirement hours (only applicable when the view is set to project) User can pass any combination of applicable metrics seperated by comma (i.e. planned,actual). _Default value of `data` is_ **`planned`**.
+**daily_hrs** `optional` | This parameter defines whether the result should contain a daily breakup of hours or not. If the parameter with the true value exists in the request, then the response will include daily utilization hours along with the aggregated total utilization hours. _Default value of `daily_hrs` is_ **`false`**.
+
+
+Along with query parameters, this API endpoint also accepts filter criteria as a request body. Kindly refer to the examples shown to the right. To learn more about filters, visit this section.
+
+### Returns
+
+| Code | Description |
+| ---: | :---- |
+**200** `OK` | This indicates that the operation was successful and utilization is returned.
+**400** `Bad Request` | Bad Request error occurs when a request is malformed, syntactically incorrect or when the offset or limit value is a negative integer.
+**403** `Forbidden` |Authorization failed due to insufficient permissions. This occurs when user does not have enough access rights to perform this action. Access for each user can be controlled by an Administrator using eRS Cloud Application.
\ No newline at end of file
diff --git a/source/index.html.md b/source/index.html.md
new file mode 100644
index 00000000000..42248ea36ed
--- /dev/null
+++ b/source/index.html.md
@@ -0,0 +1,32 @@
+---
+title: eRS Cloud API Reference
+
+
+language_tabs: # must be one of https://git.io/vQNgJ
+ - shell
+
+toc_footers:
+
+includes:
+ - introduction
+ - authentication
+ - errors
+ - udftypes
+ - resourcetypes
+ - projecttypes
+ - requirementprofile
+ - bookingprofile
+ - timesheetprofile
+ - calendars
+ - resource
+ - project
+ - requirement
+ - booking
+ - rates
+ - timesheet
+ - utilization
+ - filter
+search: true
+
+code_clipboard: true
+---
\ No newline at end of file
diff --git a/source/index.md b/source/index.md
deleted file mode 100644
index 4c1fa8c9f7d..00000000000
--- a/source/index.md
+++ /dev/null
@@ -1,168 +0,0 @@
----
-title: API Reference
-
-language_tabs:
- - shell
- - ruby
- - python
-
-toc_footers:
- - Sign Up for a Developer Key
- - Documentation Powered by Slate
-
-includes:
- - errors
-
-search: true
----
-
-# Introduction
-
-Welcome to the Kittn API! You can use our API to access Kittn API endpoints, which can get information on various cats, kittens, and breeds in our database.
-
-We have language bindings in Shell, Ruby, and Python! You can view code examples in the dark area to the right, and you can switch the programming language of the examples with the tabs in the top right.
-
-This example API documentation page was created with [Slate](http://github.com/tripit/slate). Feel free to edit it and use it as a base for your own API's documentation.
-
-# Authentication
-
-> To authorize, use this code:
-
-```ruby
-require 'kittn'
-
-api = Kittn::APIClient.authorize!('meowmeowmeow')
-```
-
-```python
-import kittn
-
-api = kittn.authorize('meowmeowmeow')
-```
-
-```shell
-# With shell, you can just pass the correct header with each request
-curl "api_endpoint_here"
- -H "Authorization: meowmeowmeow"
-```
-
-> Make sure to replace `meowmeowmeow` with your API key.
-
-Kittn uses API keys to allow access to the API. You can register a new Kittn API key at our [developer portal](http://example.com/developers).
-
-Kittn expects for the API key to be included in all API requests to the server in a header that looks like the following:
-
-`Authorization: meowmeowmeow`
-
-
-
-# Kittens
-
-## Get All Kittens
-
-```ruby
-require 'kittn'
-
-api = Kittn::APIClient.authorize!('meowmeowmeow')
-api.kittens.get
-```
-
-```python
-import kittn
-
-api = kittn.authorize('meowmeowmeow')
-api.kittens.get()
-```
-
-```shell
-curl "http://example.com/api/kittens"
- -H "Authorization: meowmeowmeow"
-```
-
-> The above command returns JSON structured like this:
-
-```json
-[
- {
- "id": 1,
- "name": "Fluffums",
- "breed": "calico",
- "fluffiness": 6,
- "cuteness": 7
- },
- {
- "id": 2,
- "name": "Isis",
- "breed": "unknown",
- "fluffiness": 5,
- "cuteness": 10
- }
-]
-```
-
-This endpoint retrieves all kittens.
-
-### HTTP Request
-
-`GET http://example.com/api/kittens`
-
-### Query Parameters
-
-Parameter | Default | Description
---------- | ------- | -----------
-include_cats | false | If set to true, the result will also include cats.
-available | true | If set to false, the result will include kittens that have already been adopted.
-
-
-
-## Get a Specific Kitten
-
-```ruby
-require 'kittn'
-
-api = Kittn::APIClient.authorize!('meowmeowmeow')
-api.kittens.get(2)
-```
-
-```python
-import kittn
-
-api = kittn.authorize('meowmeowmeow')
-api.kittens.get(2)
-```
-
-```shell
-curl "http://example.com/api/kittens/2"
- -H "Authorization: meowmeowmeow"
-```
-
-> The above command returns JSON structured like this:
-
-```json
-{
- "id": 2,
- "name": "Isis",
- "breed": "unknown",
- "fluffiness": 5,
- "cuteness": 10
-}
-```
-
-This endpoint retrieves a specific kitten.
-
-
-
-### HTTP Request
-
-`GET http://example.com/kittens/`
-
-### URL Parameters
-
-Parameter | Description
---------- | -----------
-ID | The ID of the kitten to retrieve
-
diff --git a/source/javascripts/all.js b/source/javascripts/all.js
index ffaa9b01307..5f5d4067ba6 100644
--- a/source/javascripts/all.js
+++ b/source/javascripts/all.js
@@ -1,4 +1,2 @@
-//= require ./lib/_energize
-//= require ./app/_lang
+//= require ./all_nosearch
//= require ./app/_search
-//= require ./app/_toc
diff --git a/source/javascripts/all_nosearch.js b/source/javascripts/all_nosearch.js
index 818bc4e5095..026e5a20039 100644
--- a/source/javascripts/all_nosearch.js
+++ b/source/javascripts/all_nosearch.js
@@ -1,3 +1,27 @@
//= require ./lib/_energize
-//= require ./app/_lang
+//= require ./app/_copy
//= require ./app/_toc
+//= require ./app/_lang
+
+function adjustLanguageSelectorWidth() {
+ const elem = $('.dark-box > .lang-selector');
+ elem.width(elem.parent().width());
+}
+
+$(function() {
+ loadToc($('#toc'), '.toc-link', '.toc-list-h2', 10);
+ setupLanguages($('body').data('languages'));
+ $('.content').imagesLoaded( function() {
+ window.recacheHeights();
+ window.refreshToc();
+ });
+
+ $(window).resize(function() {
+ adjustLanguageSelectorWidth();
+ });
+ adjustLanguageSelectorWidth();
+});
+
+window.onpopstate = function() {
+ activateLanguage(getLanguageFromQueryString());
+};
diff --git a/source/javascripts/app/_copy.js b/source/javascripts/app/_copy.js
new file mode 100644
index 00000000000..4dfbbb6c06d
--- /dev/null
+++ b/source/javascripts/app/_copy.js
@@ -0,0 +1,15 @@
+function copyToClipboard(container) {
+ const el = document.createElement('textarea');
+ el.value = container.textContent.replace(/\n$/, '');
+ document.body.appendChild(el);
+ el.select();
+ document.execCommand('copy');
+ document.body.removeChild(el);
+}
+
+function setupCodeCopy() {
+ $('pre.highlight').prepend('');
+ $('.copy-clipboard').on('click', function() {
+ copyToClipboard(this.parentNode.children[1]);
+ });
+}
diff --git a/source/javascripts/app/_lang.js b/source/javascripts/app/_lang.js
index 1a124bb68ae..cc5ac8b6bd8 100644
--- a/source/javascripts/app/_lang.js
+++ b/source/javascripts/app/_lang.js
@@ -1,3 +1,5 @@
+//= require ../lib/_jquery
+
/*
Copyright 2008-2013 Concur Technologies, Inc.
@@ -13,13 +15,14 @@ WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations
under the License.
*/
-(function (global) {
+;(function () {
'use strict';
var languages = [];
- global.setupLanguages = setupLanguages;
- global.activateLanguage = activateLanguage;
+ window.setupLanguages = setupLanguages;
+ window.activateLanguage = activateLanguage;
+ window.getLanguageFromQueryString = getLanguageFromQueryString;
function activateLanguage(language) {
if (!language) return;
@@ -28,11 +31,13 @@ under the License.
$(".lang-selector a").removeClass('active');
$(".lang-selector a[data-language-name='" + language + "']").addClass('active');
for (var i=0; i < languages.length; i++) {
- $(".highlight." + languages[i]).hide();
+ $(".highlight.tab-" + languages[i]).hide();
+ $(".lang-specific." + languages[i]).hide();
}
- $(".highlight." + language).show();
+ $(".highlight.tab-" + language).show();
+ $(".lang-specific." + language).show();
- global.toc.calculateHeights();
+ window.recacheHeights();
// scroll to the new location of the position
if ($(window.location.hash).get(0)) {
@@ -93,7 +98,7 @@ under the License.
// gets the language set in the query string
function getLanguageFromQueryString() {
if (location.search.length >= 1) {
- var language = parseURL(location.search).language
+ var language = parseURL(location.search).language;
if (language) {
return language;
} else if (jQuery.inArray(location.search.substr(1), languages) != -1) {
@@ -124,11 +129,16 @@ under the License.
history.pushState({}, '', '?' + generateNewQueryString(language) + '#' + hash);
// save language as next default
- localStorage.setItem("language", language);
+ if (localStorage) {
+ localStorage.setItem("language", language);
+ }
}
function setupLanguages(l) {
- var defaultLanguage = localStorage.getItem("language");
+ var defaultLanguage = null;
+ if (localStorage) {
+ defaultLanguage = localStorage.getItem("language");
+ }
languages = l;
@@ -137,7 +147,9 @@ under the License.
// the language is in the URL, so use that language!
activateLanguage(presetLanguage);
- localStorage.setItem("language", presetLanguage);
+ if (localStorage) {
+ localStorage.setItem("language", presetLanguage);
+ }
} else if ((defaultLanguage !== null) && (jQuery.inArray(defaultLanguage, languages) != -1)) {
// the language was the last selected one saved in localstorage, so use that language!
activateLanguage(defaultLanguage);
@@ -155,8 +167,5 @@ under the License.
activateLanguage(language);
return false;
});
- window.onpopstate = function() {
- activateLanguage(getLanguageFromQueryString());
- };
});
-})(window);
+})();
diff --git a/source/javascripts/app/_search.js b/source/javascripts/app/_search.js
index 91f38a04edf..0b0ccd97fdd 100644
--- a/source/javascripts/app/_search.js
+++ b/source/javascripts/app/_search.js
@@ -1,49 +1,76 @@
//= require ../lib/_lunr
+//= require ../lib/_jquery
//= require ../lib/_jquery.highlight
-(function () {
+;(function () {
'use strict';
var content, searchResults;
var highlightOpts = { element: 'span', className: 'search-highlight' };
+ var searchDelay = 0;
+ var timeoutHandle = 0;
+ var index;
- var index = new lunr.Index();
+ function populate() {
+ index = lunr(function(){
+
+ this.ref('id');
+ this.field('title', { boost: 10 });
+ this.field('body');
+ this.pipeline.add(lunr.trimmer, lunr.stopWordFilter);
+ var lunrConfig = this;
+
+ $('h1, h2').each(function() {
+ var title = $(this);
+ var body = title.nextUntil('h1, h2');
+ lunrConfig.add({
+ id: title.prop('id'),
+ title: title.text(),
+ body: body.text()
+ });
+ });
- index.ref('id');
- index.field('title', { boost: 10 });
- index.field('body');
- index.pipeline.add(lunr.trimmer, lunr.stopWordFilter);
+ });
+ determineSearchDelay();
+ }
$(populate);
$(bind);
- function populate() {
- $('h1, h2').each(function() {
- var title = $(this);
- var body = title.nextUntil('h1, h2');
- index.add({
- id: title.prop('id'),
- title: title.text(),
- body: body.text()
- });
- });
+ function determineSearchDelay() {
+ if (index.tokenSet.toArray().length>5000) {
+ searchDelay = 300;
+ }
}
function bind() {
content = $('.content');
searchResults = $('.search-results');
- $('#input-search').on('keyup', search);
+ $('#input-search').on('keyup',function(e) {
+ var wait = function() {
+ return function(executingFunction, waitTime){
+ clearTimeout(timeoutHandle);
+ timeoutHandle = setTimeout(executingFunction, waitTime);
+ };
+ }();
+ wait(function(){
+ search(e);
+ }, searchDelay);
+ });
}
function search(event) {
+
+ var searchInput = $('#input-search')[0];
+
unhighlight();
searchResults.addClass('visible');
// ESC clears the field
- if (event.keyCode === 27) this.value = '';
+ if (event.keyCode === 27) searchInput.value = '';
- if (this.value) {
- var results = index.search(this.value).filter(function(r) {
+ if (searchInput.value) {
+ var results = index.search(searchInput.value).filter(function(r) {
return r.score > 0.0001;
});
@@ -53,10 +80,10 @@
var elem = document.getElementById(result.ref);
searchResults.append("